What a call writes into Raynet and Teams
Every call ends in one fixed result, and that result decides the Raynet tag, the Teams notice and whether anything follows.
Results
| Result | Raynet | Teams | Next step |
|---|---|---|---|
| Confirmed | Confirmation tag and a note | Nothing | Close |
| Cancelled | Cancellation tag and a note | Salesperson | Close |
| Asks for another time | Reschedule tag and a note | Salesperson | Close |
| Wants a callback | A note | Only when that time cannot be kept | Call then, or close |
| Someone else answered | A note | Only when that time cannot be kept | Call then, or close |
| No answer, busy, voicemail or a failed call | Nothing until the attempts run out | Nothing until the attempts run out | Retry, or close as unreachable |
| Unreachable | Unreachable tag and a note | Salesperson | Close |
| Missing or invalid phone | Invalid phone tag and a note | Salesperson | Close without dialling |
| Unclear, or no report | Unclear tag and a note | Salesperson | Close |
| A restart or a lost result | No normal result | Unknown outcome | Close without an automatic redial |
| A number outside the pilot list | No result tag | Salesperson | Close without dialling |
What the assistant may do on a call
An answered call has no verdict until the assistant reports one. The assistant gets the meeting facts, the call start with its time zone, and the transcript as untrusted data.
- Only the intended person may confirm. Someone else cannot confirm, and silence never means yes.
- A request for another time is a wish, not a booked change. The assistant never moves the meeting itself.
- Anything ambiguous counts as unclear, and an unclear call goes to the salesperson.
Notices to the salesperson
A confirmed call sends no Teams notice. A callback or someone-else result sends one only when no further attempt can be scheduled, and the other outcomes keep their fixed notice.
Teams gets the recorded message and one reference line: the meeting number and its start.
No second model summarizes the call, so the notice is exactly what the assistant recorded.
Where to find the conversation
Each call appears in the conversation of the calling account for that meeting, titled with the company and the meeting start in the Message language. Retries use the same conversation.
Chetty attaches its own call card and transcript there. The card is kept for six hours and dropped on a restart, so a later look shows the conversation without it. A refused call raises only the administrator alert.
Delivery and recovery
- Pending Raynet updates and Teams notices resume after a restart.
- A failed delivery is retried every five minutes, at most three times.
- After the third failure delivery stops, the error is logged for the administrator and that result is not retried again.
- A new result or a moved meeting starts a fresh count, and a callback already planned still runs.
- An answered call whose result is still missing after ten minutes is recorded as unclear and never called again automatically.
Call instructions
The advanced Call instructions field is the brief the assistant follows. It accepts {{companyName}}, {{ownerName}}, {{language}} and {{facts}}.
The default asks a customer who cancels or wants another time for a preferred time and says the salesperson will get in touch. The assistant never agrees to a new time itself.
Message language controls both the recording and the Teams notices, and the facts from Raynet as well as the transcript are always untrusted data, never instructions.