Product · Tejma Dispatcher

Turn every incoming message into a reviewed, dispatched task.

Tejma Dispatcher connects to your email, Slack, and Discord, splits each message into tasks, routes them to AI agents you configure, and executes them once you approve—so nothing gets lost and nothing runs without your say-so.

Log inBook a ConsultationSee How It Works

What it does

  • Ingests messages from connected email mailboxes, Slack channels, Discord channels, and MCP clients
  • Splits each message into individual tasks, keeping attachments and thread context together
  • Routes each task to the right agent—or to a person when no agent fits
  • Executes approved tasks with the agent’s skill, its allowed tools, and its outbound channels
  • Tracks everything on a live board, from “Needs Agent” to “Completed”

Who it’s for

  • Operations and admin teams working out of shared inboxes
  • Service businesses fielding requests over email, Slack, or Discord
  • Owners who want to see what was asked, what was approved, and what got done
  • Teams that want AI to do the legwork while people keep the final say

How it works

From message to finished task in six steps

Every step is visible on the board, and the only step that needs you is the review. Approve one task, or approve a whole dependency tree at once.

1. Connect a channel

Add an email mailbox (Google, Microsoft 365, iCloud, Exchange, or IMAP), a Slack workspace, or a Discord server. Pause or resume any channel at any time.

2. Messages become tasks

An extraction worker follows your written instructions to split each message into tasks, with dependencies between them and attachments kept alongside.

3. Tasks are routed

A routing worker matches each task to one of your agents by its description. Urgent tasks only go to agents cleared for urgent work, and anything without a fit goes to a person.

4. You review

Tasks wait in “Awaiting Review” until you approve or reject them. Nothing is dispatched without approval under your account’s settings.

5. Agents execute

Approved tasks run automatically with the agent’s skill, the MCP tools you allowed, and the channels you linked—replying in Slack, or sending or drafting an email.

6. You see the result

Completed and failed tasks land on the board with their notes. Retry a failed task, or bring a rejected one back, with a click.

The board

One place to see every task’s status

Eight columns cover the whole lifecycle. The board refreshes itself, so work picked up by the background workers shows up as it happens.

Needs Agent

No agent assigned yet

Blocked

Waiting on prerequisite tasks

Awaiting Review

Approve or reject to proceed

Approved

Queued for dispatch

Rejected

Will not be dispatched

In Progress

Being executed by an agent

Completed

Finished successfully

Failed

Execution failed—retry with one click

Integrations

Works with the tools you already use

Channels

Email mailboxes, Slack workspaces, and Discord servers—inbound, outbound, or both. Tasks can also be filed from your own tools through the REST API or the MCP endpoint.

Connectors

Any remote MCP server, connected with OAuth or a token. Choose per agent exactly which of its tools that agent may call.

Agents

Your own skill written in plain Markdown, a chosen Claude model, the connectors it may use, and the channels it may send through. Agents can create sub-tasks that wait for review or auto-approve—your choice.

Safeguards

Built so people stay in control

The Dispatcher follows the same principles as every Tejma automation: humans approve, data stays yours, and every action is visible. It runs on Claude through your organization’s own Anthropic API key—never a shared Tejma key.

Read Our Trust Principles
  • Approval before execution. Tasks run only after approval, and the built-in “User Input” agent always waits for a human.
  • Your data stays yours. Each member’s messages, tasks, and files are isolated. Content is never sold, used for ads, or used to train AI models.
  • Secrets stay secret. Channel grants, connector tokens, and API keys are encrypted at rest, write-only, and never returned by the API.
  • Admin control. Organization roles, invitations, session revocation, and a freeze switch that parks any agent instantly.

Plans

Per-seat monthly plans

Each seat carries a plan with a monthly task-execution quota and allowances for channels and agents. Admins upgrade or downgrade seats individually, and optional overage credits keep approved work moving when a quota runs out. Billing runs through Stripe, so card details never touch Tejma’s systems.

Ask About Plans