WhatsApp Business
Your business number
Customers message your connected WhatsApp Business number. Replies return to the same chat, subject to WhatsApp messaging rules.
Connect WhatsAppTurn customer questions into progress. Tephlo brings your knowledge, products, and enabled business tools into conversations across WhatsApp, Telegram, your website widget, and API-connected apps.
Not all are open to new workspaces. See what each may not say
Answers use the workspace’s available business content.
A saved cart is not a placed or paid order. Your team confirms the sale.
Recording a refund request does not issue a refund. Handoff needs a configured team route.
Illustrative conversations, not a live chat. Capabilities require setup and permission.
Meet customers in the apps they use, on your website, or inside a product you build. Connect the channels you need to your Tephlo workspace.
Customers message your connected WhatsApp Business number. Replies return to the same chat, subject to WhatsApp messaging rules.
Connect WhatsAppCustomers message your connected bot in private chats and get replies in Telegram, using your workspace’s content and enabled tools.
Connect TelegramAdd the chat widget to your approved website domains. Visitors can ask for help and read replies without leaving your site.
Add the widgetYour server sends customer messages with scoped API keys. Fetch replies when ready, or use signed webhook notifications to know when to fetch them.
Explore the APIUses available business information, checks what it is allowed to do, and prepares an answer or an authorized next step.
WhatsApp, Telegram, and widget replies return through their original channel. For the API, your application retrieves and displays the reply.
Authorized teammates can review conversations in the workspace and take over when needed. Configure a handoff route for requests that need a person.
Channel features can differ. Availability depends on your plan, workspace access, and connection setup. API replies are asynchronous; production API access requires workspace approval.
Bring answers, products, requests, and conversations together. Available actions depend on your plan, assistant profile, enabled features, and connected data; your workspace shows what is ready to use.
Add policies, guides, and articles to Knowledge. Review processed content and keep its approval and validity current. Tephlo uses eligible sources to answer questions, with checks designed to limit unsupported facts and actions.
Give customers help with routine questions and enabled tasks. Your team can take over conversations, review captured requests, and handle decisions that need human approval. Set up an eligible handoff route before relying on escalation.
Describe your organization, the work you want help with, and the decisions your team should keep. Guided setup proposes an assistant profile and shows its capabilities and outstanding setup needs before you activate it.
Use the settings pages or fill in a Word or Markdown setup template. Review extracted values before applying them; uploading alone changes nothing. Guidance documents have their own review and activation steps and do not grant permissions.
Connect WhatsApp Business, Telegram, your website widget, or an API-powered application. Availability depends on the connection, provider, and your workspace settings; conversations remain accessible to authorized teammates.
Manage products directly in Catalog or import supported catalog files through Knowledge. Product names, prices, options, stock, and specifications come from the active structured records.
With catalog and cart capabilities enabled, Tephlo can help customers compare products, collect items and quantities, and submit a potential order for workspace review. Your team confirms the sale, payment, and fulfillment.
With customer memory enabled and workspace consent in place, saved preferences and relevant context can help personalize later conversations. Customer privacy controls also cover stored memory.
Enabled request workflows capture details for orders, appointments, viewings, quotes, callbacks, complaints, and refund requests. Booking and order requests appear on Appointments and Orders, where your team can book an open time or build the order from the catalog in one step, and the customer is told. A recorded refund request does not issue a refund.
Set goals and preferred next steps for your business. Conversation state can carry selected products, quantities, and open questions forward so customers can continue an active flow.
Where organization defaults are assigned, your workspace can inherit them and show which settings you have customized. Keep useful defaults, override individual values, or reset eligible fields to their organization default.
Smart Updates is off by default and requires platform availability, workspace opt-in, approved content, and explicit customer consent. Eligible sends are limited to twice a month, at least 14 days apart. Customers can ask for fewer updates, pause, or reply STOP to opt out.
When enabled, an unfinished conversation can qualify for one follow-up attempt: options shown, a price or quote given, a booking or enrolment left open. The system rechecks replies, declines, human takeover, and channel messaging windows before sending, and a sector programme writes the message for its situation. Your workspace can turn this off.
Add photos for a catalog product or anything else you sell in one step. Say whether they show the exact item or the same model, and the assistant tells the customer which when it sends them. Delete a product and its photos go with it. Publishing content and enabling customer delivery are separate steps, with readiness shown in Media.
Choose which of the six certified languages your workspace answers in. A customer who writes in Nigerian Pidgin, Yorùbá, Hausa or Igbo is answered in that language, in the tone they used; the honesty checks that read the reply run in every one of the six. Voice, image, and document processing depend on the formats and features available to your workspace; review these settings before offering them to customers. Your team reads in its own language too: a complaint written in Hausa or an order note in Yorùbá can be rendered into a teammate's reading language with one click, the original kept beside it.
Review unanswered and repeated questions, improve source material, and manage approval and validity. Where answer reuse is enabled, current permission and content checks still apply.
Review conversation activity, automation and escalation metrics, captured requests, and usage. Reporting distinguishes available measurements from figures that have not been measured.
Install Tephlo from the browser on Android or iPhone — no app store. Each teammate sees the work their role allows: customers waiting, orders to approve, appointments to confirm. They reply, approve and confirm from there and, where notifications are on, get an alert when something new needs them. Get the phone app
Content Home brings together failed uploads, pending approvals, expiring content, broken product-media links, and stale Smart Updates. Follow each item back to the place where you can review it.
Tell us what kind of organization you are and the assistant follows a program written for that kind of business, in English and French. The direction it adds is short. The refusals are the part worth reading: our code checks the draft reply for a list of sentences and takes them out before your customer sees them. A sector program can only ever make the assistant do less. Six of the nine carry refusals that run in code. Three carry none, and this list says which.
In a lending workspace the assistant drafts an approval, our code removes that sentence before delivery, and the same check hands the conversation to the person who actually decides, with everything the customer already said. Your customer gets a human, not a gap.
A refusal is a typed value in our code with one of six effects: withhold the sentence, hand the turn to one of your people, stop the questions and point to emergency care, remove a capability for that turn, hold the workspace at our regulated level, or block an unprompted message. There is nothing in a sector program that grants a new power, and no prompt written by you or your customer widens one. Every withheld sentence ships with the exact wording it must catch, in English, French, Nigerian Pidgin, Yorùbá, Hausa and Igbo, and a refusal missing any of them is rejected when the code loads. A separate test fails if an ordinary sentence is caught instead.
Direction onlyNo sector refusal runs in code here.
Written directionRecommend only products that appear in your evidence, at their exact prices and only with the benefits it states; invent no stock, scarcity, discount or delivery time. The platform guards that are not sector-specific still apply.
Direction onlyNo sector refusal runs in code here.
Written directionQuote scope, price and timing only from your evidence, and never say a slot is free, held, reserved or arranged.
1 checked in codeWithheld: “Your table is confirmed for 8pm tonight.” The sentence is taken out of the reply before delivery, and nothing here hands the conversation to a person.
Written directionA request is not a reservation; invent no availability, hours, menu, room, price or capacity, and never say a table is being held.
2 checked in codeWithheld: “Done — you are now enrolled in the evening course and your place is confirmed.” “Good news, you’re accepted onto the programme” is withheld the same way. Neither hands the conversation to a person.
Written directionTeach only from the material provided, hint before the worked answer, and invent no course facts. Enrolment stays with your office.
2 checked in codeWithheld: “You’re approved for the tenancy, congratulations.” The attempt itself hands the conversation to one of your people.
Written directionMatch on the facts of the property, never on who someone is, and never call a viewing arranged or an offer accepted.
2 checked in codeWithheld: “You’re approved for the assistance program.” That turn goes to one of your people.
Written directionAsk only what the application requires and ground every impact figure in your material. Before your team verifies, “appears to qualify” is the most it may say.
8 checked in codeWithheld: “Take 2 tablets of 500 mg every six hours until it settles.” Naming a condition, and saying that a prescription, referral or record was sent, are checked for too. The cart is removed, unprompted messages are off, the workspace is held at our regulated level, and when a message carries one of the listed emergency wordings the reply opens with a line pointing to emergency care and the turn goes to a person.
Written directionIntake, not answers. General health information only from your approved material; a patient-specific answer belongs to a clinician.
5 checked in codeWithheld: “This plan has a guaranteed return of 12% a year, risk-free.” “Good news, you’re approved for the loan” is withheld the same way, and an eligibility decision hands the conversation to one of your people. Unprompted messages are off and the workspace is held at our regulated level.
Written directionRates, fees, terms and eligibility only as your evidence states them; a projection is never a promised return; advice only a licensed adviser may give goes to that adviser.
Direction onlyNo sector refusal runs in code here.
Written directionLearn how this organization works from your evidence and from the customer, and prefer a concrete answer to a general one.
Twenty refusals run in our code across these six trades: eight, five, two, two, two and one. Two more are written down and only restate a confirmation the platform already makes, so we do not count them. Every sentence quoted here is a real string in our code, and each ships with a test that fails if it stops being caught.
There is no healthcare assistant and no financial-services assistant to buy here. We wrote both profiles and we hold both back. A regulated workspace should be able to force every generated recommendation to a person before it is sent; our code cannot yet tell an answer that recommends from one that informs, so it cannot do that, and both profiles fail our own check for exactly that reason.
A clinic or a lender is set up on our general business assistant instead: answers from your own material, captured requests, handover to your team, workspace media. No catalog and no order status. The healthcare or financial program then adds its direction and its refusals on top, and holds the workspace at our regulated level — a second factor and a person here before it can be activated, durable customer memory off, no reuse of one customer’s answer for another, a written statement of what the assistant is for, and approval decisions and urgent requests mandated to reach a person. Of the three kinds of decision that level names, we enforce those two. The third is the recommendation problem above, and it is why the two profiles stay off the menu rather than on it.
That is less than the name of the sector suggests, and it is what you get today.
Certified here means our own review, not anyone else’s. Before a program can be published we replay 57 to 75 scored scenarios for that sector through the real assistant in English and French, 579 in all, then run the same set on a live model and have a second, different model score every reply against a written rubric; a run that judges itself is refused before it starts. A pass needs both stages and a mean of at least 3 out of 5 on every dimension, where 3 is defined as acceptable and 5 as what a strong professional in that trade would say. Healthcare and financial also need a second administrator, not the author, to sign off the exact wording. Every scenario was written by us; none of it is customer traffic. No outside body has assessed any of it. It is not a clinical, financial or regulatory certification, and choosing a sensitivity level is not a compliance claim.
These checks read the draft reply in all six languages and look for the listed wordings and their near neighbours. A determined paraphrase can get past them, and no refusal here covers a fact the assistant simply gets wrong. The emergency check recognises listed wordings; it is not a symptom checker and it assesses nothing. A certificate is bound to the wording, the refusal list and the renderer it was earned under: change one and it goes stale, and nothing can be published until the tests run again. It is not a statement about the whole assistant. Programs are switched on one trade at a time, and a program only reaches a workspace that has been pinned to it; a workspace that has not adopted one behaves exactly as it did before. The refusals and emergency lines run in all six languages; the coaching the model reads is written in English and French.
That is the whole list. The one thing it cannot tell you is whether the program for your trade is open to new workspaces yet, so ask us and we will answer plainly.
Ask which programs are open to new workspacesSee what it can act onUse the built-in catalog, potential orders, and calendar with the capabilities your workspace has enabled. Choose how much appointment authority to give the assistant.
Add and edit products in Catalog, or review products detected in supported Knowledge imports. Add photos to a catalog product straight from Media. Appointment services are configured separately in Booking setup.
When enabled, the assistant can collect items and quantities, save the cart, and submit a potential order for workspace review. That is not a placed, paid, or shipped order. Tephlo does not collect card data; your workspace contacts the customer, confirms the order, collects payment, and handles fulfillment outside this built-in workflow.
Booking setup covers services, providers or resources, workspace timezone, booking hours, and time off. Collect requests without offering times, offer times for team confirmation, or enable automatic confirmation. An auto-confirm flow reports a booking only after the slot is reserved successfully. Manage appointments and their cancellation or rescheduling from the calendar.
Start with a suitable profile, prepare the content and services it needs, then test your customer experience before going live.
Review the proposed assistant profile, available capabilities, and inherited defaults. Set your goals, guidance, and human handoff route.
Review Knowledge sources, manage Catalog products, publish Media, and complete Booking setup for the workflows you plan to offer.
Connect WhatsApp Business, Telegram, your website widget, or an API integration. Complete the relevant access and connection checks, then test representative questions and requests before serving customers.
Workspace permissions, review steps, and privacy tooling help your team manage customer conversations and the data behind them. Review the controls that apply to your setup.
Your own figures, every assumption we add printed beside them, and the answer on screen without giving us an email address.
Enquiries that arrive when nobody is working, and enquiries that queue behind other enquiries at your busiest hour, priced against your own close rate and order value.
Open the calculator →What one ticket costs you in salary, and how much of a month goes on tracking, booking, account and FAQ questions that never needed a person.
Open the calculator →Partners share a link and earn a commission on what the businesses they bring actually pay, for a set number of months, paid against a monthly statement. A person or a company, not a workspace.
Connect a channel, add your knowledge and business data, and let Tephlo resolve the work you have approved.