SZ.chat implementation and management for WhatsApp support and sales
We are SZ Chat (Fortics) partners and we handle the SZ.chat implementation end to end: official WhatsApp API connection, chatbot flows, queues, agent scheduling and broadcasts with a Meta-approved template. Once you go live, the operation stays with us: flow adjustments, queue monitoring and a monthly report. You see what each conversation costs.
What the SZ.chat implementation covers
If you are looking for SZ.chat, you have already picked the tool. What you still need is someone to configure it, integrate it and keep it running.
Implementation and official API connection
We create the account, connect the official WhatsApp API and set up users, departments and business hours. We test the full message path before opening it to the public.
Chatbot flows: how it works in practice
We design the support tree: what the bot handles on its own, what it qualifies and the exact point where it hands over to a person. Every flow is reviewed by someone who did not build it before it goes live.
Queues, departments and agent scheduling
We set up queues by topic, how conversations are distributed across agents and the on-call schedule, including outside business hours. Whoever is on call knows what they receive and at what time.
WhatsApp broadcasts with a Meta-approved template
We write the template, submit it to Meta for approval and prepare the contact list for the broadcast. Without an approved template there is no bulk sending on the official API — and that is where most campaigns stall.
Integrations through the SZ.chat API
We connect SZ.chat to what the company already uses: management system, ERP, store, spreadsheet or automation. The conversation stops being an island and starts reading and writing data where it actually lives.
Monthly report and cost per conversation
Every month we cross paid traffic with the conversations opened in SZ.chat and show the cost per conversation. That is the number that tells you whether to raise the budget or change the flow.
Chatbot knowledge base
We use the client’s real support history to write the bot’s answers, in the language the team already uses. When it makes sense, we run AI models on our own server, with no cost per query and without the data leaving the environment.
Ongoing operation
We track the queue, response time and the points where people drop out of the flow in a weekly sprint. Support flows age: prices change, processes change, and so does the question that comes in most.
SZ.chat operations already running with us
Three steps, no surprises along the way
1. Diagnosis with data
We look at message volume, the questions that come in most, who answers today and at what time. That reading is what shapes the queues, the flow and the schedule — not a generic template.
2. Implementation
Configuration, flows, templates and integrations, testing the full path before opening. Our house rule applies: whoever built it does not check it, whoever checked it does not approve it.
3. Weekly optimization
A weekly sprint to adjust flow, queue and broadcasts based on real conversations. At the end of the month, the cost-per-conversation report closes the cycle and points to the next adjustment.
Questions about SZ.chat
How does SZ.chat work and what can you automate in it?
SZ.chat is the Fortics platform that connects the official WhatsApp API to a support center: several people on the same number, with queues, history and a chatbot. You can automate the initial triage, answers to repeat questions, data collection before human support and routing to the right department. Anything that calls for a decision, negotiation or sensitivity stays with a person — the bot is there to get you to that person faster.
How do you set up agent scheduling and queues in SZ.chat?
First we split the queues by topic, because the topic is what defines who is able to answer. Then we link each agent to the departments they cover and define how conversations are distributed and each person’s hours. Outside business hours and on peak dates, we set up an on-call schedule with a named owner, so no conversation is left without one. We run exactly this format in memorial parks, with on-call coverage on weekends as well.
How do you send bulk messages with a Meta-approved template?
On the official API, any message started by the company needs a Meta-approved template before it can be sent. We write the text within the rules, submit it for approval, clean up the contact list and schedule the broadcast through SZ.chat. Then we track deliveries, replies and opt-outs, because a badly run broadcast burns the list and can cost you the number’s quality rating.
How much does each conversation cost on the official WhatsApp API, and how do you measure it?
The official API price is set by Meta and varies by message category and by country, on top of the platform subscription — so the correct figure is always the official rate card in force when you sign up, and we check that with you before turning the broadcast on. What we actually measure is your business’s cost per conversation: paid traffic budget plus platform and message costs, divided by the conversations opened in the period. We deliver that number in the monthly report.
Can the SZ.chat chatbot be connected to a CRM or to the company’s system?
Yes, through the SZ.chat API and the API of the system on the other side. We have already integrated support with management systems and automation, using n8n, Python and our own database when state needs to be stored. The limit is what the other end exposes: if your system has no API or documentation, we check that during the diagnosis before promising the integration.
Tell the urutau about your challenge
It answers right away and, if needed, brings in one of us. No strings attached.