Get alerts for new cases
Choose alerts that bring your team back to the inbox. Open Templ to read a case's messages and details. An owner or Admin connects team channels. An Admin's channels pause if that person loses Admin access.
| Channel | Set it up |
|---|---|
| Browser In testing | Allow browser notifications from Templ. Keep the app open. |
| Verify your alert email in Settings and choose case alerts. | |
| Slack In testing | Add an approved Slack destination in Alerts and send a test. |
| Discord In testing | Add an approved Discord webhook in Alerts and send a test. |
| Telegram In testing | Add your Telegram destination in Alerts and send a test. |
| Webhook In testing | Save an HTTPS endpoint and verify its signed events. |
These team channels send alerts. Read and answer cases in Templ. Check email alert availability before relying on delivery. Verifying your email address does not enable delivery.
Reply through Telegram
Telegram replies is a separate integration. Templ must enable it for your workspace before you connect it. An owner or current human Admin can then approve Templ's bot for one Telegram group. When the AI needs help with a general question, the group receives a linked case summary. It shows what the AI answered and what it still needs. Reply to that message. The AI asks a follow-up when an essential fact is missing. Once it has the answer, it posts a proposed reply in Telegram. A current group administrator reviews it and clicks Send reply. Nothing reaches the user before approval. Reply to the proposal to request changes. The same approval button handles requests for a person. Sensitive account cases stay human-led. If AI drafting is unavailable, the team reviews its original reply before sending.
The AI can save reusable product facts that the team confirms. Ask it to add a public docs link or retire an outdated source. Retired sources remain in the workspace's history. Private case details stay out of reusable knowledge. Group administrators can read handed-off cases and reply there. Anyone in that group can read the copied notices, replies and drafts. Review who belongs to the group. Disconnecting or removing the approver's Admin access ends the integration's case access.
Read alert contents
Slack, Discord and Telegram team-channel alerts carry the event, counts or waiting time, a fixed code and an authenticated link. They never contain message, note or tag text. They exclude names, emails, wallets, transaction hashes, amounts and access levels. Email case notices also leave out private case text and wallet details. A user's confirmed reply email contains a single-use case resume link.
A signed webhook can carry wallet and shared transaction details when the owner enables them for that endpoint. Only the owner can change a channel that shares wallet details. Keep webhook signing keys private. Verify the signature before using an event. An alert grants no case access.
Check workspace setup and the team inbox. Never include a private key or recovery phrase in an alert.
In testing means the feature is built and not yet open to every workspace.