Use Tephlo across WhatsApp, Telegram and web chat, with shared content and a console for your team. Start with setup, then follow the guide for the work you want your assistant to handle.
Each workspace has its own assistant configuration, channels, business information and customer conversations. The assistant can answer from your Knowledge, catalog and configured business facts; use available read integrations; and carry out actions allowed by its active profile and current workspace state.
Built capabilities include saved carts and order requests, internal appointments, customer requests and complaints, reviewed media sharing, and consent-based Smart Updates. Voice transcription and audio replies have separate settings. Your team can review conversations, take over when needed, and maintain the material the assistant uses.
Business claims should be supported by available evidence. Behavior instructions, goals and guidance shape communication; they do not grant an action or make a business fact true. Server checks determine whether a tool may run and whether it succeeded. When evidence or a capability is missing, the assistant should explain the limit and use an available next step. Review real conversations as part of operating it.
A saved cart or submitted request does not take payment, place a commerce order, reserve stock or start fulfilment. Scheduling records a request or confirms an internal appointment, depending on your setup; it does not synchronize Google Calendar or Outlook. See catalog and carts, appointments and action limits.
New workspace? Create your account and follow the quickstart, including the activation checklist. Plans and current offers are on the pricing page.
Complete onboarding, activate a profile, review content and test a channel.
Connecting customers to the assistantWhatsApp Business, Telegram and the web widget — shared sandbox versus your own credentials.
Configuring how the assistant helpsBehavior, Goals, reviewed templates, Agent Guidance and organization defaults.
Writing the material the answers come fromUpload and review sources, maintain validity and distinguish processing from approval.
Helping shoppers move from a question to a reviewable requestStructured products, saved carts and the workspace-reviewed potential-order workflow.
Managing what customers see and hearPhotos of your products and services, incoming media and assistant audio replies.
Keeping interested customers informedApproved updates, customer consent, sending eligibility and outreach controls.
Offering appointment times without creating calendar conflictsServices, resources, availability and the difference between a request and a confirmed time.
Understanding what customers will actually getGrounded answers, the capability limits enforced in code, handoff, goals per domain, and languages.
Support agents and workspace adminsA tour of every screen your team works in, and who can reach which one.
Teammates who work away from a deskInstalling it on Android and iPhone, what each teammate sees, notifications and what stays on the desktop.
Organizing workspace responsibilitiesTeammate invitations, built-in and custom roles, and effective access.
Developers integrating over HTTPAuthentication, a five-call quickstart, idempotency, errors, signed webhooks and environments.
Security review and procurementTenant isolation, encrypted credentials, audit trails, consent defaults and privacy tooling.
Anyone stuck on one specific thingShort answers to the questions that come up during setup.
This documentation describes implemented workflows. Availability still depends on platform switches, your plan, workspace policy, profile activation, required data and provider readiness. A visible setting or saved preference does not establish that customer delivery is enabled.