A functional test of a Righthand conditional quote acceptance
Test: Supply a quote for Friday delivery. Tell the teammate customer to accept only with Tuesday delivery.
A customer reply can accept a price only with another condition. The assistant must keep that condition.
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
Supply a quote for Friday delivery. Tell the teammate customer to accept only with Tuesday delivery.
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 supplied quote question to the identified teammate.
>
Send any acceptance condition to the owner.
>
Keep delivery unchanged without approval.
>
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 teammate accepts only if delivery moves to Tuesday. The original offer remains Friday.
The owner gives a decision about whether to give Tuesday as an alternative before giving confirmation of acceptance.
The acceptance conditions
The result must identify conditional acceptance and the different requested date.
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.
Reporting an unconditional accepted order 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.