Invoices, support cases and frequent questions solved by the customer in minutes — and human support one tap away when needed. Your team handles only what truly requires people.
Most conversations are always the same — and they arrive outside business hours.
Invoice copies, case status, account updates: simple requests that eat up the team queue.
Customers need answers at night and on weekends — not only during service hours.
Time spent on routine work instead of the cases that truly need human attention.
WhatsApp self-service flows, connected to your Salesforce.
From request to payment without talking to anyone.
Check and update cases right in the conversation.
Handoff at any moment, with full context.
The relationship team received a high volume of repetitive requests — invoice issuing and case tracking — and customers depended on service hours to get anything done.
With chatt2.me, the company deployed WhatsApp self-service integrated with Salesforce: customers identify themselves by ID number, get invoices with PDF and barcode, comment on cases and, if needed, talk to an agent.
Service available 24 hours, frequent requests solved in minutes by customers themselves and the team dedicated only to cases that require human attention — with the full history in Salesforce.
Customers solve things whenever they need, without depending on business hours.
Invoices and case status leave the support team queue.
Queries and requests solved in minutes, with no waiting.
Invoice with PDF and barcode on the spot; cases updated in the conversation itself.
The team steps in when self-service isn't enough — already with full context.
Every interaction logged on the case, ensuring continuity of service.
The case on this page uses chatt2.me for Salesforce, with everything logged in the CRM. But self-service flows connect to your system — ERP, help desk or CRM — via API and webhooks.
Yes. The same API covers WhatsApp, Instagram, Messenger, Telegram, SMS and WebChat — the flows are the same, the channel is whichever your customer prefers.
By an account identifier — in the construction company's case, the national ID number. The bot validates it against your system and only then exposes that customer's invoices and cases.
Yes. Invoices and cases are examples: any query or request your system exposes through an API can become a self-service flow.
It depends on the integrations. Flows like the ones on this page — identification, lookup and document delivery — usually go live in a few weeks.