One round trip
From /command to a reply in three seconds
- Step 1Someone types it/deploy staging
- Step 2Enclessa calls youWith a sealed bearer token
- Step 3You answerWithin three seconds
The whole budget. Longer work acknowledges now and posts later through a webhook.
in_channel
Everyone in the room sees it
Stored like any message, tagged with the command.
default
Only the caller sees it
Never written down: not searchable, exported or retained.
Built in, on every plan
The commands people use constantly
They run in the client, with autocomplete as you type.
Custom commands
Your endpoint, safely called
- How do I register a custom command?
- Someone who may manage the team registers it against a URL. That provisions a bot account, which joins a room the first time the command is used there. Each outbound request carries a sealed bearer token so your endpoint can verify the caller.
- What stops a command from being used to probe our network?
- The address is checked inside the dialer, on the address actually connected to, so a DNS record pointing at 127.0.0.1 does not get through. Private and loopback ranges are refused unless an installation explicitly opens them.
What it does not do
The edges, before you find them
- Three seconds is the whole budget. Longer work acknowledges at once and posts later through a webhook.
- Replies are text: no buttons, menus, modals or forms.
- Custom commands are team-scoped. There are no organisation-wide or per-channel commands.
- Managed rooms only. A command bot cannot join an end-to-end encrypted room.
- A command runs when somebody types it, never on a schedule or trigger.
FAQ
Slash commands: questions
- Yes. Built-in commands cover joining and leaving channels, inviting people, sending direct messages, setting a channel header, starting a call and searching. Teams can also register custom commands that call an HTTP endpoint they control.
- Someone who may manage a team registers a command against a URL. When it is used, Enclessa posts a request carrying a sealed bearer token, waits up to three seconds, and renders the reply either into the channel or privately to the person who typed it.
- Yes. A reply that is not marked in_channel goes back only to the person who typed the command, and it is never written to the message store — so it cannot be searched, exported or retained.
Bring your team over this afternoon
Free for up to 10 people, with encrypted direct messages and video calls. No payment card, no time limit, no server to run.
For businesses and organisations only — not available to consumers.