Righthand
← All posts

Use Slack for a shift swap approval question

Example: Two staff members discuss swapping reception shifts. The supervisor did not accept the revised coverage.

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

Two staff members discuss swapping reception shifts. The supervisor did not accept the revised coverage.

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 shift discussion.

>

Prepare the proposed coverage for the supervisor.

>

Identify original and proposed shifts as different states.

>

Get approval before a roster change.

>

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.

Agreement between participants does not always establish scheduling authority.

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 proposal covers both shifts but has no supervisor approval. The original roster remains the accepted source.

The supervisor gives a decision about the swap before the assistant changes any available roster record.

Try one account task

  1. Give the Righthand one identified source record.
  2. Compare its result with that source.
  3. Examine the account record after a permitted write.
  4. 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.

Compare plans. Get a Righthand.