Use case
meiti on meiti: our support and sales run on the same tools as yours
We are our own first customer. meiti's support, our sales and every message to customers run through the same inbox, the same assistants and the same public API as yours. That way we talk to every customer personally — and automate everything that can be automated.
One inbox for everything
- Support on WhatsApp and phone: our assistant answers, handles standard questions and opens a ticket. Each plan has its own entry point, so requests land in the right place.
- Developer support: a separate number for integrations — WhatsApp or call, no email.
- Help requests from the app: when a customer taps "Request a local number", a ticket opens on our side with their account as context. The app shows them the request is already in progress.
Personal where it matters — automatic where it can be
Automatic
What the assistant and our systems handle.
- Answer, sort, handle standard questions
- Open a ticket with contact and account
- Summary and task after every conversation
- Signals from our systems arrive via the API
Personal
What our team takes over.
- Walk through setup together, call back
- Review every draft before it goes out
- Coordinate internally: team chat, notes, handover
- Call out — straight from the ticket
Account care through our own API
We're building the next step right now: our systems spot accounts that need help — setup not finished, no call forwarding, WhatsApp not connected, trial ending, no calls or failing calls. For each account they call our own public API and drop a ready draft into our inbox. A team member reviews and sends it.
It's the same API you use for your software. What works for us works for you — and the other way round.
Why this fits SaaS support and outbound
- One timeline per customer: calls, WhatsApp, email and signals from your system in the same ticket.
- No tool zoo: no separate ticket system, dialer or SMS gateway.
- Automate without losing control: drafts instead of blind sending, the team approves.
- Your system stays current: webhooks report every conversation, the API writes back.