Skip to main content

Answer cases in the team inbox

Your team answers private in Inbox. Each case keeps the messages and shared details together.

Team inbox

Inbox views and tools

Choose a view​

ViewWhat belongs here
Needs youA case needs a person from your team.
AI is handlingAn active can answer the user.
Waiting on userYour team or AI replied and waits for the user.
ResolvedThe case is closed. Older cases can show a recorded user confirmation.

Needs you shows why a person must act:

  • The user asked for a person. Older cases can also show a Not solved response.
  • The AI handed off the case.
  • The case uses only or AI off.
  • No AI agent is active or its answer did not arrive within the allowed wait.

More views include assigned, unassigned, open, spam, abandoned and archived cases. Search shows cases you can read with current access.

Priorities​

Priorities In testing

Templ can turn on Priorities for one while its hosted checks are pending. When on, the inbox opens on Priorities. It shows open cases that need your team, with the highest score first. Open a case to answer the user.

Read the reasons​

Each case shows short tags that explain its place in the feed.

Example tag or detailWhat it means
VerifiedThe user proved this wallet for this workspace.
Deposits about $1.2MThe has deposits in your app's selected contracts.
About $1.2M at 14:02 UTCThe deposit snapshot was checked at that time.
Transaction amount 1,250 USDCThe case shows the app-reported amount. This amount does not raise its priority.
Waiting 12 minThe case has waited for a team reply.
ReopenedThe user reopened the case.
Repeat contactThe user has another case in this workspace.
Transaction failedThe AI handed off a case about a transaction.
Safety checkThe AI handed off a case about safety.
Asked for a personThe user asked your team to answer.

Top depositor and Large depositor mark app deposits above the manager's set values. Every eligible case gains priority while waiting for your team. A long wait can outweigh a new case's deposit boost. Other show their reason.

Check wallet proof​

Claimed, not verified means the app supplied the wallet address without proof. That wallet never raises the score. Choose Ask to verify wallet to send the case's wallet sign-in request. The user decides whether to sign in.

Set priorities​

Owners and Admins can save Priority settings.

  • Top deposits USD starts at $100,000.
  • Large deposits USD starts at $10,000.
  • Reply target minutes starts at 15 minutes.
  • Deposit contracts selects supported contracts from your app profile.

Configure your app's Ethereum or Base ERC-4626 vaults backed by native USDC. Templ reads the verified wallet's shares and converts them to the underlying amount. Vault reads check the underlying asset at the same block as the shares. General wallet token balances never count as app deposits. Native USDC uses $1 per token. Other networks, assets and receipt adapters remain unverified for Priorities. Missing adapters, reads or prices show unavailable values and add no deposit boost.

Templ reads positions when the user verifies their wallet. Opening a case refreshes positions after 6 hours. Changing the counted deposit contracts allows a fresh read on the next case open. The same daily quotas and provider limits apply. The feed uses cached values and never polls the network. Position reads use their own 2 configured providers and RPC limits.

Keep case data private​

Only staff with current case access see deposit values, depositor tags and scores. Removing staff access ends those reads. Users and widget sessions never receive these fields. User exports exclude them. The feed ranks cases inside your workspace.

Read reports​

Managers and can open Reports. Counts and median reply times cover cases opened during the selected period. First reply includes AI replies. First human reply counts a person's reply. These times start when the case opens. Waiting for reply counts cases that currently need your team. All retained excludes archived history. Check the update time and any notice about incomplete history.

Read the case​

Open your workspaces, choose the workspace and open Inbox. The case panel shows the wallet label, failure snapshot, and history. Transaction checks separate chain facts from app reports and unknowns. A transaction hash proves no wallet ownership.

Reply or add a note​

Write in Reply to answer the user. Write in for your team. Users never receive notes. User exports exclude internal notes. Use saved replies for answers your team approved. A adds notes and handles follow-ups under their current case access.

ShortcutAction
EnterSend the reply.
Shift+EnterAdd a line.

Check the composer before sending. A restored draft never sends itself. Never ask for a private key or recovery phrase.

Take over and resolve​

Choose Take over from AI to switch the case to AI drafts only. A person's reply, claim, assignment or typing makes the same switch. Assignment shows who handles the case; it grants no support access. Choose Resolve when the team finishes helping. Visitors can send another message in the same chat. A reply within the reopen window reopens the case. Silence counts as neither visitor confirmation nor a billing event. See case billing.

Set the name users see​

Set Your name for users in Settings. Users see that name with a small Team tag. With no name set, they see Team. Display names confer no permission. AI agents never trigger the person-joined line. Users see “A person from the team joined” when a person first replies, claims or receives the case.

Respect a stop​

Stop team messages stops replies, initiation and reopening, including managers and AI agents. The user can still read retained messages. Only the user can ask again and lift the stop.

Read AI modes and new-case alerts to plan the next reply.

In testing means the feature is built and not yet open to every workspace.