Key takeaways
- The brief has a service and city from your own lists, up to six details and one neutral sentence.
- Contact details are stripped before the model sees anything, and again from what it writes back.
- The AI never sees your member list, profiles or profile answers, and it never chooses who is asked.
- One clarifying question at most. Anything still unclear goes to your team.
What goes into the AI request summary
| Field | What it holds |
|---|---|
| Service | One skill from your community's list, or blank if none fits |
| City | One city from your list, or blank if the member didn't say |
| Must happen in a place | Yes for in-person needs such as property or catering, no for remote work such as software |
| Details | Up to six short facts, for example size, budget, timing or rent or buy, in English |
| Summary | One neutral sentence in English, under 140 characters, with no names or contact details |
| Language | English, Hinglish or other, shown to your team when it isn't English |
A service or city the model suggests that isn't on your lists is dropped, not added. Your lists stay the only vocabulary matching uses.
What the model sees, and what it never sees
- It sees the member's message with phone numbers, emails and links replaced by placeholders such as [phone].
- It sees the names of your skills and cities, so it can pick from them.
- It never sees your member directory, anyone's profile, answers to your profile questions or any phone number.
- A long run of digits is treated as a phone number even when it might be a price. Removing too much is the safe side.
- The message is handled as data. Instructions written inside it, such as asking the model to change its rules, are ignored.
- What comes back is checked before use: lengths are capped and anything that looks like a contact detail is removed again.
When the AI can't write a usable brief
| What happened | What Milvao does |
|---|---|
| The service, or a city the need depends on, is unclear | Asks the member one question, written by Milvao rather than by the model |
| Still unclear after that one question | Hands the request to your team under Needs you |
| The model failed twice, or its answer didn't fit the brief format | Hands it to your team as Milvao couldn't read this request |
| The member edited the brief three times | Hands it to your team to sort out with them |
An operator can then read the original message, write or fix the brief with Edit brief, and Milvao sends it to the member to confirm.
The member decides whether the brief is right
- 1The brief arrives with Confirm, Edit and Cancel buttons, usually within a few seconds.
- 2Edit lets the member send a corrected request in one message. Buttons on the older brief stop working.
- 3Confirm moves on to a separate question about sharing their number.
- 4If your team later changes the service, city or summary of a confirmed brief, the member is asked to confirm again before any new offer goes out.
How AI calls are recorded
Every call is written to Milvao's separate logs database with the redacted input, the model, token counts and whether it worked, and is kept for 90 days. Matching itself uses Milvao's own ranking rules, described on automatic member matching, so no AI decides who gets asked. Anthropic is listed with Milvao's other sub-processors.
Sources
- Milvao Help Center: How requests work (checked 5 November 2026)
- Milvao Help Center: Your data and how long we keep it (checked 5 November 2026)
Facts about WhatsApp and other services come from the pages listed, on the dates shown, and can change.