Skip to main content
Home is where you supervise your engagement team. It shows what is waiting for your decision, what the team is doing, and what Tranthor recommends, and it lets you either build something yourself or tell the team what to do.

​
What’s on the Home page

  • Composer. One box with two modes. Build it myself starts a conversation with the Tranthor Assistant to build a campaign or answer a question. Tell the team talks to the Supervisor, which answers questions about your engagement team. Home remembers the mode you last used. Starter plays appear as chips in the empty composer.
  • Needs you. Everything waiting for your decision, in one list.
  • Team. Each Objective with its status, goal and next run, plus the Autonomy level and Recent activity. On a wide screen this sits beside the main column. On a narrow screen it collapses to a one-line summary that expands.
  • Recommendations. Campaign ideas based on your own customer data.

​
Needs you

Needs you is the one place you decide what the team has prepared. It holds three kinds of items:
  • Proposals the team prepared on its own, for you to approve.
  • Delegated items: drafts from a Recommendation you handed to the team.
  • Team change items: a pause, a resume or a goal change that the Supervisor wrote for you to confirm.
Team changes you asked for come first, then Proposals ordered by urgency (anything expiring or out of date first), then delegated items. The first item is open and the rest are one line each. Home shows the first five, and Show more reveals up to ten; an item you open from a link is always shown. If more are waiting, a link takes you to Agents. The number on the bell in the header is the same count as this list. Each Proposal and delegated item says in one sentence why it exists, then shows the audience, the channel and the schedule. A team change shows what will change instead. A warning appears only when something is off: the send is close to your per-action limit, the contact policy is not active, the proposal is about to expire, or it is out of date. On a Proposal you can:
  • Preview the message. A draft stored as an email template (MJML or React Email) cannot be rendered on Home, so the preview says so and you review it in the Objective.
  • Approve. The button states what happens, for example “Approve and send to 4,210”. Your name and the time are recorded with the decision.
  • Request changes, then describe what should change. Your note is saved with the decision and the Supervisor can read it, but the team does not redraft the Proposal from it; its next scheduled run plans from scratch. A delegated draft is different: the agent redrafts it from your note.
  • Reject.
Some items cannot be approved from Home. The card tells you why:
  • The Objective is paused. Resume it, then approve. You can still reject or request changes while it is paused.
  • The proposal has expired or is out of date because the goal, the contact policy or the Objective’s settings changed after it was prepared. Home cannot start the re-evaluation itself: open the Objective in Agents, review the proposal there, and choose Re-evaluate Proposal when it reports the conflict.
  • The audience has not been verified yet.
  • No approved contact policy is attached to the proposal.
Experiment proposals are reviewed from the Agents page, because they can never be approved for automatic execution. If part of the list cannot be loaded, Home shows what it did load and says that the list may be incomplete.

​
The team

Each Objective shows whether it is Active, Paused or Drafting, its goal and when it runs next, with links to edit the goal and the contact policy. Use Pause or Resume on an Objective to stop or restart it. A paused Objective drafts nothing new and stops any approved send before its next recipient. Proposals that were already waiting stay in Needs you.

​
Autonomy level

One control sets how much the team may do without asking. Open it from the team section. Verify before send is the active level: the team drafts and you approve every send. Ask first and Autonomous are shown but locked, each with the reason. An Objective that was already set to send on its own shows as Autonomous, and you can lower it to Verify before send at any time. Lowering a level does not make waiting proposals out of date.
Email campaigns built from an approved email design are always reviewed by a person before they send, whatever the level. See Engagement team.

​
Recent activity

The last five events: a person approving, rejecting or asking for changes on a proposal, a send, or a team change that was confirmed or dismissed, and by whom.

​
Tell the team

In Tell the team, ask the Supervisor what the team did, what is waiting, or how an Objective is doing. It answers from your workspace’s data and says so when the data cannot answer. The Supervisor can also set up the team, and it can prepare a pause, a resume or a goal change for an Objective. It never makes the change itself: it writes a confirm card that you confirm or dismiss in the chat or in Needs you, where it stays for 24 hours. The Supervisor cannot send anything, change an Autonomy level or change an operating policy. You do those yourself.

​
Recommendations

Recommendations are chosen from audiences Tranthor can verify in your data, for example a saved segment with no campaign yet, customers who have lapsed or are at risk, or your most engaged customers. A recommendation is only suggested when its audience has at least 50 customers. Counts are a snapshot at the time the recommendation was made. They show how many customers match, not how much revenue is at stake. Each recommendation has two actions:
  • Build myself starts a conversation in the composer with that recommendation as context.
  • Delegate asks the team to draft it. The row shows Drafting while the team works, and the finished draft appears in Needs you as a delegated item. Nothing sends until you approve it. Delegate is available when Tranthor can pin the audience exactly: a saved segment, or one of the verified customer groups such as lapsed customers or your most engaged customers. For a customer group, the team reads who is in it when it starts and saves that list as its own segment, named for the group and the draft, so the draft reaches exactly those customers even if you later build the same group yourself. The group can have changed since the recommendation counted it, so the finished row tells you how many customers the draft is for when that differs. If the list does not finish loading in time, or the group is now under 50 customers, the draft fails, nothing is drafted or sent, and you can try again. For any other audience Delegate is disabled and the row says why. Build myself is always available.
While Tranthor is still analyzing a new workspace, Home shows starter plays. These are generic until tailored recommendations are ready.

​
The Tranthor Assistant

In Build it myself, there is one assistant and no agent to pick. Ask it to:
  • build a broadcast,
  • set up a journey workflow, or
  • answer questions about performance and customers.
Analytics questions are read-only. When you start from a recommendation, the assistant keeps it as context for follow-up questions until you start a new chat. AI outputs may contain mistakes. Check important information before you act on it.

​
Approve from Slack

If your workspace connects Slack, link your own Slack user under Settings, Integrations so Slack approvals are recorded against you. A Slack user who has not linked cannot approve or reject from Slack, and is told how to link.