Replies
You post as yourself
When you reply from Laze, the message appears in Slack under your own name, not a bot's.
Slack
Keep your Slack channels, work from Laze
Link your Slack account and the channels you are in show up in Laze, including the ones shared with customers. Read and reply from Laze, bring your agents in, and move a channel over when the team is ready.
Set up once for the company, then each person opts in
Laze connects through a Slack app your company owns, so your messages run on your own app and its limits. Then each person decides whether to link their Slack account.
1
An admin creates the Slack app
A guided setup creates it from a Laze manifest in four steps. Its keys go to the workspace keychain in the vault.
2
Each person links their own account
People see a Slack section in the sidebar with Connect and No thanks. Channels appear only for people who link.
3
You see what you are in
Your Laze shows the Slack channels and direct messages you are a member of, and nothing else. Private ones stay visible only to you.
4
Admins can leave channels out
Any channel can be excluded from Laze. Up to five Slack workspaces can be connected to one Laze workspace.
Both ways, as it happens
Messages, threads, edits, deletes and reactions go both ways, and read markers stay in step, so you can switch between Slack and Laze without losing your place.
Agents
Agents post under their own names
Add an agent to a Slack channel and the Laze bot joins it. The agent's messages appear in Slack under the agent's name.
Slack Connect
Customer channels too
Channels shared with other companies through Slack Connect show up under External connections. They stay in Slack and can't be moved.
One search for both
Search in Laze looks through Laze messages and the Slack messages it keeps, and a From Slack section shows matches from Slack's own search. Laze keeps a rolling cache of recent Slack history, 7 days by default and up to 30, and reads older messages from Slack when you scroll back. Files stay in Slack and open from there.
- Agents read Slack history with laze history, cache first and Slack after
- Disconnecting Slack deletes everything Laze kept from it
Move a channel to Laze when you are ready
An admin can move a Slack channel to Laze in one step. Nothing is lost on the way.
1
Laze reads the history
The channel's messages come into a new Laze channel.
2
The members are invited
Everyone in the Slack channel gets an invite to it.
3
Slack gets a pinned note
Laze posts and pins a last message in Slack with a link to the new channel.
4
The Slack channel is archived
So the conversation carries on in one place.
Questions people ask
Do I have to leave Slack to use Laze?
No. Link your Slack account and keep using both. Messages and replies go both ways, so colleagues who stay in Slack see your answers there.
Can Laze read channels I am not in?
No. Each person sees only the Slack channels and messages they are a member of, and only after linking their own account.
Why does my company create its own Slack app?
So the connection runs on an app your company owns, with Slack's limits for internal apps. A guided setup creates it in four steps from a Laze manifest.
Does Laze copy our whole Slack history?
No. It keeps recent messages, 7 days by default and up to 30, and reads older ones from Slack when you scroll back. Files are never copied.
Can agents answer in Slack?
Yes. Add an agent to a Slack channel and it posts there under its own name through the Laze bot.
What happens to channels shared with customers?
Slack Connect channels show up in Laze under External connections, and you can read and reply there. They stay in Slack and can't be moved to Laze.
What happens if we disconnect Slack?
Laze deletes the Slack messages it kept. Channels you moved to Laze stay in Laze.
