Concierge
Ask Frimas
Type, speak, drop a photo or share your location. Prices and availability come from the booking engine, never from the model.
What Frimas remembers
Stored on this device only. Nothing here is sensitive and you can delete any line.
Language
Or just write in Arabic or Arabizi and it will follow you.
WhatsApp channel
Same engine, same customer record, same tools. This is a simulator, not a connected WhatsApp number.
Proactive sequence
The customer never asks where the van is. Frimas tells them. Play the sequence a live job would send.
Message flow
WhatsApp Cloud API
↓ webhook, signature verified
↓ session and identity by phone number
↓ understanding layer, model swappable
↓ tool router with authorisation
↓ booking engine and data
↓ result composed into a reply
↓ WhatsApp
No business logic sits in the WhatsApp handler, which is why the web console and a future voice line reuse all of it.
AI operations
Every tool call the assistant made, in order. If it is not in this list, it did not happen.
Tool call log
Improvement queue
Requests the assistant could not resolve. These are the things to teach it next.
Real, and simulated
| Component | Status |
|---|---|
| Language understanding | Real model call, with a keyword fallback if it fails |
| Voice input | Real browser speech recognition |
| Photo understanding | Real vision call, confidence shown |
| Location | Real browser geolocation |
| Pricing and availability | Real deterministic engine, not the model |
| Customer memory | Real, stored on device |
| Simulated. Needs Meta Cloud API and a verified number | |
| Payment | Simulated. Amount is owned by the engine, never the model |
| GPS and temperature | Simulated series. Ingestion boundary is built |
| Human handover | Simulated. Routes to a queue, no agent desk yet |