Milkchoc
Contacts: michael-cleary | richie-ragel | anthony-milkchoc | jessica-milkchoc
Recent meetings: 2025-08-05-milkchoc-oneai-sync
Account Summary
Milkchoc is an Australian property management company (PropTech) that engaged OneAI in August 2025 to explore an AI voice agent for triaging tenant maintenance queries. The use case is well-defined — high inbound call volumes, integration with PropertyMe CRM, and strict caller verification requirements. Only one meeting has taken place and there has been no confirmed follow-up since; Michael Cleary held outstanding action items that were never confirmed received.
Use Case
AI voice agent to triage inbound tenant maintenance queries at scale:
- Triage agent — handles high-volume inbound calls from tenants reporting maintenance issues, qualifying and routing queries before escalating to human staff
- PropertyMe CRM integration — agent must read/write to PropertyMe to log maintenance requests and verify tenant details
- Caller verification — security-first requirement: callers must be verified to banking-grade standards before any sensitive information is shared or actions are taken
Relationship Health
🔴 At Risk — Only 1 meeting on 2025-08-05, now 10+ months ago. Account never confirmed live or progressed past the initial sync. Michael Cleary’s action items (process map, call recordings, staff interview setup) were never confirmed received. No cadence established.
Key Contacts
- Michael Cleary (mc@milkchoc.com.au) — Primary contact; owns the process map documentation, call recording samples, and staff interview coordination. The only contact with a named action item.
- Richie Ragel (rr@milkchoc.com.au) — Attended the initial sync; role not specified.
- Anthony (anthony@milkchoc.com.au) — Attended the initial sync; role not specified.
- Jessica (jessica@milkchoc.com.au) — Attended the initial sync; role not specified.
What’s Working
- Use case is clearly scoped from the first meeting: triage agent, PropertyMe integration, caller verification — a concrete brief to build from
- High inbound call volume signals a genuine operational pain point and strong ROI potential for an AI agent
- Four stakeholders attended the initial sync, suggesting internal buy-in across the team
Open Challenges
- No follow-up contact since August 2025 — the account has been dark for 10+ months with no confirmed re-engagement
- Michael’s deliverables (process map with call flow diagrams, call recording samples, volume data, staff interview arrangements) were never confirmed received — unknown whether they were completed
- Caller verification to banking-grade standards adds security complexity to the agent design that needs detailed requirements work
- PropertyMe CRM integration requires technical scoping that hasn’t started
- Australian timezone (AEST/AEDT) creates scheduling friction for Daniella’s team
- No commercial terms, pricing, or next-step milestones were documented
Open Action Items
The following items were assigned to Michael Cleary at the 2025-08-05 sync and have not been confirmed received or completed:
- Create process map documentation for the property management use case (pen-and-paper diagrams of most important call flow elements)
- Provide call recording samples and volume data showing where the biggest call volumes occur
- Arrange interviews between the OneAI team (Daniella/Yochai) and relevant Milkchoc staff
Recent Meeting Highlights
- 2025-08-05 — Milkchoc <> OneAI: Sync: First and only meeting; established the triage agent use case, PropertyMe CRM integration need, caller verification security requirement, and high call volume context. Michael Cleary left with three concrete deliverables to kick off the design process.
Prep Tips for Next Meeting
Re-engagement after 10+ months dark — treat this as a near-cold outreach:
- Lead with a concise re-introduction: acknowledge the time gap directly and make it easy for them to re-engage without embarrassment about the lapsed deliverables
- Check whether Michael’s three action items were ever completed — process map, call recordings, and staff interview setup are the blockers to moving forward; ask neutrally rather than pressing
- Confirm whether the use case and priorities have shifted in 10 months — property management landscape may have changed, and PropertyMe may have released new API capabilities
- Re-validate the four attendees are still the right stakeholders; staff turnover is common over a 10-month gap
- Have a concrete “next 2 steps” ready: e.g., a 30-minute call flow review session if the process map exists, or a guided template to help Michael complete it if it doesn’t
- Note the Australian timezone when scheduling — AEST is UTC+10 (AEDT UTC+11 in summer)