Decision brief: Hand tickets over between two agents and check what the reports show

Goes with checklist version 1.0 (2026-10-06) · AI Builder Marketplace · Fill it in after your trial, then print it or save it as a PDF. It records your decision on the date below; prices and plans change after that.

Date

Decided by

What we need it for

Team size and users

Products and plans we compared

ProductPlanPrice per month, billing

Requirements

Mark each check as a must-have, a nice-to-have or not needed, then write down what you saw. We have not run these checks ourselves; the checks follow the vendor's documentation.

IDCheckNeeded?Your resultOur result
S01Assign
Assign three of the six tickets to Agent A and leave three unassigned. Per the docs, Agent A gets an email and finds them under My Tickets.
Our result: not run by us
S02Two agents on one ticket
Open the same ticket as Agent A and Agent B. Per the docs, the second sees a red alert that someone else is viewing it, and a draft in progress shows a pencil in the list.
Our result: not run by us
S03Hand over with an internal note
Agent A comments on a ticket and tags Agent B. Per the docs, B gets an email and the customer never sees comments; confirm nothing reached your sending mailbox.
Our result: not run by us
S04Reply and history
Agent B replies. Per the docs, the ticket moves to Answered on its own and the audit trail shows who assigned, commented and replied, with times.
Our result: not run by us
S05Who sees reports
Open Reports as admin, then as Agent A and as the collaborator. Per the docs, only admins can access reports.
Our result: not run by us
S06Reports against assignment
Compare the overview with Agent A's report for your test window. Per the docs, agent and team reports count only assigned tickets (three, not six), and collaborator activity does not appear.
Our result: not run by us
S07Collaborator limits
As the collaborator, try to comment, reply, assign and archive. Per the docs, commenting works and the other three do not; collaborators count as users on the price.
Our result: not run by us

Must-haves we could not check

A must-have you could not test is unknown, not passed. Write it down here and ask the vendor before you sign.

Costs

Yearly cost of the plan we need

One-off switching costs

Months paying for two tools

Work out switching costs, overlap and payback in Before You Renew (https://aibuildermarketplace.com/tools/renewal-check/). Leave a cost you do not know as unknown instead of guessing.

Open questions for the vendor

Decision

   

Product and plan

Main reason

Check again on (date)

What would change this decision

Our test report: https://supportbee.com/docs/handling-tickets/tracking-performance-with-reports