A functional test of a Righthand email recipient before customer follow-up
Test: Use two teammate addresses with similar names. Permit contact with only the first address.
An owner wants to delegate customer contact. The test must establish that the message goes to the identified address.
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 two teammate addresses with similar names. Permit contact with only the first address.
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 first identified teammate an email with the supplied collection question.
>
Keep the second address outside the task.
>
Send the reply to the 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 first teammate receives the collection question. The second receives no message under this task.
The owner examines the recipient before using the procedure for a customer.
The acceptance conditions
The permitted teammate must receive the identified question. The owner's result must keep the exact contact identity.
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 message to the second address fails this test. A prepared draft alone does not complete the requested send.
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.