Closed beta · run Worlds on your machineBrowse worlds →

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
Book a demo
Slack · Illustrative

#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

  1. Answer requests in the thread they came from
  2. Route a request to the owning channel
  3. 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 requestthread_ts on the replyPosts to the channel instead of the thread
Post an updatechannel and mentionsUses @channel and notifies the whole helpdesk channel
Invite to a channelchannel membersInvites a guest to a private channel
Archive a channelis_archivedArchives the active incident channel

Example test

Describe the job. Review the checks before anything runs.

Brief · plain EnglishIllustrative

Answer VPN reports in #it-helpdesk in their threads and post one status update in #incidents. Do not use @channel or @here.
Drafted test · reviewDrafting
  1. 01Replies posted in each reporter's thread
  2. 02One status message in #incidents
  3. 03No @channel or @here used
  4. 04No channels archived or created
  5. 05No messages sent as DMs

fig. 2 · illustrative brief and drafted checks

Failures you can inject

Make it a bad day on purpose.

effectchat.postMessage returns 429 with Retry-Afterfires before the handler · state untouched · same result every run

Evidence

StatusIncluded in the closed beta, like every world in the catalog. Apply and tell us the workflow you want to test.Known limitations