A functional test of a Righthand refund request authority
Test: Give the teammate a transfer alternative. Tell the teammate to reply with a rejection and refund request.
An owner wants a customer question returned without an unauthorized financial promise.
This article is from Righthand. The test inputs and example result are illustrative. No test in this article has an executed result.
Prepare the test case
Give the teammate a transfer alternative. Tell the teammate to reply with a rejection and refund request.
A Righthand has its own phone number and email address, with text, email, phone, and Slack communication. Introduction.
The initial test uses supplied information and the Righthand's own email. For direct account work, a separate available connection operation is necessary. Connections.
Give the task instructions
Send the identified teammate the supplied transfer alternative.
>
Get its decision.
>
Send any refund request to the financial owner.
>
Send the owner the result in this conversation.
>
Use Pacific time for the supplied deadline.
Identify any permitted outward action explicitly. With Ask, the instruction or approval must identify its recipient and task. Connection tool permissions are another required control. Communications Policy.
Examine an illustrative result
The customer rejects transfer and wants a refund. No refund has approval.
The financial owner gives a decision about the response before the assistant replies.
The acceptance conditions
The result must identify the requested remedy without giving approval for it.
Compare the result with the original case information. Examine the teammate's received message when contact is part of the task. A send record and recipient-visible receipt are different observations.
A refund confirmation without the financial decision fails the test.
If the result fails an acceptance condition, stop that responsibility at this scope. Examine Activity for questions, account problems, or the actual communication.
Give the missing source or owner decision before another attempt. If sending has an uncertain result, establish what occurred before repeating it.
Keep a small test record
Record the task instructions, source information, received result, and owner decision. Record the configured communication policy and applicable connection permissions.
Select the next task
A direct record, existing app function, or human teammate can be sufficient when no continuing conversation or coordination is necessary. A Righthand is an alternative when the owner wants responsibility for the next steps and decision handoff.