Voice, messaging, email, and web chat. Same memory, same calendar, same rules, and it never forgets which door they came through.
Each one has its own page: what it does there specifically, and a scripted run of it working.
Same agent, but each channel has its own strengths.
| VoiceSee the page → | MessagingSee the page → | EmailSee the page → | Web chatSee the page → | |
|---|---|---|---|---|
| Time to first answer | Two rings | Seconds | About a minute | Instant, on the page |
| Books tours from your live calendar | Yes | Yes | Yes | Yes |
| Recognises a returning customer | By caller ID | One thread per number | Same thread | Across your sites |
| Hands off to your team | Warm transfer, same call | Person joins the thread | Routed, summary on top | Handed over, transcript attached |
| Follow-ups until they answer | Outbound calls, in your hours | Yes | Same thread | Carries on by text or email |
| Talk or type | Talk | Type | Type | Either |
| Transcript and outcome to your PMS or CRM | Before the caller hangs up | Yes | Yes | Yes |
| Where it lives | The number you already advertise | Local numbers per property, WhatsApp | Your existing inbox | Your site, portal, and listings |
How each channel is built to behave, not a measured result. Your channel mix is set on the audit call.
The same person over one week, on three channels, and an agent that never asks them to start over.
Carried forwardUnit, move-in month, the Saturday hold, and the number to text.
Carried forwardThe tour, the pet question, and the answer, in one thread.
Carried forwardTranscript, summary, and outcome on the contact before anyone hangs up.
Scripted journey · Names, times, and property are illustrative
Whichever door they come through, they get the one agent that knows them.
Start on the phone, finish over text. The agent remembers the conversation, not the channel it happened on.
Trained on how your team actually talks, from the greeting to the sign-off, and kept the same on every channel.
Interruptions, follow-up questions, and changes of mind, handled the way a person would handle them.
Reads and writes your PMS, CRM, and calendar, so nothing has to be typed twice and nothing is answered from memory.
Answers in the language the customer opens with, and hands off to your team in yours, with a translated summary.
The questions we get about channels specifically. Everything else is on the FAQ page.
Yes, and it will if asked directly. It is built to disclose rather than to pass, and to hand off to a person the moment someone would rather have one.
Yes. It answers in the language the customer opens with and hands off to your team in yours, with a translated summary attached.
No. You pick the doors on the call, starting with the ones your inquiries already come through. The others can be added afterwards. Whichever you run, it is one agent and one memory behind all of them.
Nothing they notice. The conversation is stored against the person, not the channel, so a web chat at 11 PM can continue over text the next morning and end on a call, with the agent carrying the context and your team getting one transcript.
Yes. Calls run on the number you already advertise, texts come from local numbers per property or region, and email replies go out in the thread the inquiry arrived in. Nothing to re-print.
Over text and WhatsApp, yes: floor plans, unit photos, directions, and a pay link go inline in the thread. The link points at whichever payment path you run, your own portal or the hosted checkout we set up. Over a call it can take the payment verbally, and by email it sends the link. Card details never pass through Stomeji.