Worlds / Comms and scheduling / Slack
Slack world
A local Slack workspace with channels, threads, users, mentions and workspace policies. Test the agent that answers in threads, routes requests and posts updates in the right place.
ChannelsThreadsMentionsUser GroupsReactions
#it-helpdesk
Maya Brooks 9:02My laptop can't reach the VPN since this morning.
Helpdesk agent 9:03Thanks Maya. I opened a ticket and looped in Network.thread reply · ts 9:02
Owen Price 9:05Same for me, is VPN down?
Helpdesk agent 9:06@channel VPN is down, we're on it.@channel · 412 notified
Helpdesk agent 9:08Status update posted in #incidents.message · #incidents
fig. 1 · illustrative replica · the agent's changes land as you scroll
What's in this world
What you get when you open Slack. Seeded, local, yours to break.
Seeded records
- channels
- 30 public and private channels, some archived
- messages
- 2,000 messages with threads and reactions
- users
- 80 members, guests and bots
- user groups
- @oncall, @it-team and @finance
- policies
- Who can use @channel and post in announcements
Agent jobs you can test
- Answer requests in the thread they came from
- Route a request to the owning channel
- Post incident updates without paging everyone
What your agent can get wrong here
The reply sounds right. The record is what counts.
ActionWhat the world recordsCommon mistake
Reply to a request
thread_ts on the replyPosts to the channel instead of the threadPost an update
channel and mentionsUses @channel and notifies the whole helpdesk channelInvite to a channel
channel membersInvites a guest to a private channelArchive a channel
is_archivedArchives the active incident channelExample test
Describe the job. Review the checks before anything runs.
Answer VPN reports in #it-helpdesk in their threads and post one status update in #incidents. Do not use @channel or @here.
- 01Replies posted in each reporter's thread
- 02One status message in #incidents
- 03No @channel or @here used
- 04No channels archived or created
- 05No messages sent as DMs
fig. 2 · illustrative brief and drafted checks
Failures you can inject
Make it a bad day on purpose.
effect
chat.postMessage returns 429 with Retry-Afterfires before the handler · state untouched · same result every runEvidence
StatusIncluded in the closed beta, like every world in the catalog. Apply and tell us the workflow you want to test.Known limitations