Use Slack to record the owner of a design decision
Example: A design thread has three different color proposals. No message identifies which one the customer accepted.
Keep Slack as the source for its records. A Righthand can use available information for the decision below.
This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.
The customer task
A design thread has three different color proposals. No message identifies which one the customer accepted.
Provider documentation. The documentation gives information about posting messages to identified channels. For private-channel messages, the app must be a channel member.
Make account access explicit
For Slack requests and replies, use the Slack setup guide. The bot must be in the intended conversation.
Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.
For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.
Connection Permissions gives information about account access and tool permissions. Give only the access necessary for the identified task.
The request to the Righthand
Read the supplied design thread.
>
Identify proposals and explicit customer decisions as different states.
>
Send the unanswered color decision to the account lead.
>
Send the owner the result before 3 PM Friday.
>
Use Pacific time.
Use the provider records for the result
Identify the exact conversation and its audience. Use the channel or thread supplied by the owner. For a message to a mixed or outside audience, the applicable communication permission is necessary.
The most recent message is not automatically a final decision.
For a permitted write, examine the resulting account record. A proposal does not establish a completed change.
For an external message, identify the recipient and permitted task. Ask uses an explicit instruction or approval. Connection tool permissions are another required control. Communications Policy.
An illustrative result and next step
The thread has three proposals. There is no supplied customer acceptance for any proposal.
The account lead gets the decision before the designer uses a color as approved.
Try one account task
- Give the Righthand one identified source record.
- Compare its result with that source.
- Examine the account record after a permitted write.
- Examine the work in Activity.
If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.
When the account tools are sufficient
Use Slack directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.