A Righthand test of a sent message and actual receipt
Test: Use a teammate recipient. Record the assistant's send result and the teammate's actual receipt independently.
An owner wants recipient-visible proof for an important customer instruction.
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
Use a teammate recipient. Record the assistant's send result and the teammate's actual receipt independently.
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 an email with the supplied instruction.
>
Send the sending result.
>
Get the teammate's receipt confirmation through the test 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 assistant gives a send result. The teammate gives confirmation of whether the message arrived.
The owner examines actual receipt before customer use of the route.
The acceptance conditions
The owner must keep both observations and any delay or absence.
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.
Treating a send record alone as recipient-visible proof fails the evidence requirement.
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.