The everyday questions,off your desk.
Hours, balances, gate codes, autopay, address changes. It resolves the routine requests on the spot, verifies who it is talking to first, and hands the rest to your team with the context attached.
The same five questions,all day long.
The front desk is a call center
What are your hours. What is my balance. I forgot my gate code. Each one is easy, and together they take the whole morning.
After hours, nobody answers
A tenant locked out at 10 PM or a member who cannot get into the building on Sunday gets voicemail. The problem is still there on Monday.
Account details go to the wrong person
A gate code or a balance read out to whoever calls is a problem waiting to happen. Verification takes time your team does not have.
How it works
01
It verifies
Confirms the caller matches the phone number or email on the account before sharing anything.
02
It answers
Hours, directions, balances, access codes, and policy questions, from your records.
03
It acts
Updates the address, turns on autopay, sends the receipt, or adds a unit.
04
It hands off
Anything it should not decide goes to your team with the transcript attached.
The whole job done,not a demo of it.
Verified contact only
Balances, access codes, and account details go only to the phone number or email on file. An unverified caller gets a polite no and a way to prove it is them.
Channel of record
Every request is anchored to the customer's account. The same person can call, text, and email and it is one conversation, not three.
Answers from your own records
Hours, gate access, amenities, and policies come from your knowledge base and PMS. If it is not written down, it does not get said.
Account changes in the conversation
Address updates, autopay enrollment, adding a unit, or requesting a receipt happen without a form or a callback.
Urgent issues escalate at once
Someone locked in a unit or a building without power is not a support ticket. It routes to your on-call contact immediately.
Sees the upsell
An existing customer who needs a second unit or a bigger office gets it handled in the same conversation, no transfer.
A support call, end to end.
Live transcript in the middle, the actions it took on the right.
- Duration
- 01:12
- Sentiment
- ▲ Positive
- Intent
- Reserve a unit
- Qualified
- ✓ Yes
- ✓Checked availability · 10x10 units
- ✓Pulled access hours and add-ons
- ✓Reservation held · C-114 · Saturday
- ✓Texted confirmation
- ✓Written to PMS · manager notified
- (281) 555-01489:41 AMReserved
- (713) 555-01929:26 AMQualified
- (832) 555-01078:58 AMTransferred
- (936) 555-01738:31 AMWrong number
- (281) 555-01668:04 AMReserved
Sample workspace · Names and figures are illustrative
Where it runs.
On your main line, your support inbox, and your website, with your PMS as the source of truth.
- Channels
- Voice, SMS, WhatsApp, email, web chat
- Verification
- Phone or email on file, plus your own rules
- Source of truth
- Your PMS and knowledge base
- Account actions
- Address, autopay, receipts, add-ons
- Escalation
- On-call contact, warm transfer, or ticket
- Logging
- Every request on the customer's record
How does it know who it is talking to?
It matches the caller's number or email to the account on file. From a new number, it asks for details only the account holder would know, or sends a code to the contact on record. Your verification rules are configurable.
What happens when it cannot help?
It tells the customer plainly, opens a ticket or transfers to your team, and includes the transcript so nobody has to ask the same questions twice.
Can it take a payment?
Yes, through the Payments agent. It points the caller at the payment path you already run, or takes the payment in the conversation through hosted checkout. Card details go to the processor and never pass through Stomeji.
Will it answer questions about a property it does not know?
No. It answers from the records you connect. For anything outside them, it takes a message for your team rather than guessing.