Coming soon
Planned channels for teams that want email conversations and concise SMS updates in the same controlled workflow.
The customer context
Email inbox and SMS messaging remain visible in the Telp channel roadmap. Both are planned and are not active customer channels yet.
Coming soon
Define the mailbox, sender and customer workflow that should be supported.
Confirm channel availability, consent and commercial requirements before rollout.
Test threading, delivery, handoff and opt-out behavior before customer use.
Email context alongside other customer conversations
Controlled SMS notifications for agreed use cases
A clear rollout status before either channel is activated
Telp
Lifecycle, tools and handoff remain controlled by the Telp platform.
AI replies and human follow-up remain visible in the same conversation trail.
Provider approval, account terms and separate fees are stated where they apply.
FAQ
Yes. A focused single-channel pilot is often the clearest way to validate knowledge, handoff and the first customer workflow before expanding.
Yes. Telp keeps the conversation history and handoff state in the shared operator inbox.
Not always. Some messaging and phone channels require an approved business account, number or provider fee outside the Telp subscription.
Explore related pages
Website
A lightweight embedded assistant for visitors who need an answer or next step without leaving your website.
Shareable
A shareable public conversation page for QR codes, email signatures, partner pages and support links.
Voice
Click-to-talk voice conversations in the browser, with transcript, usage visibility and operator takeover.
Tell us the channel, current process and first result you want to improve. We will suggest a focused rollout path and the cases your team should test.