Now in private beta

The support inbox for every customer channel.

Weft turns shared Slack channels, Teams, Discord and email into one calm queue. Your team replies as themselves, and customers never type a command.

Book a demo

Inbox

Todo

MWebhook retries stop after 3 attempts

SlackMaya Chen · Northwind

Webhook retries stop after 3 attemptsTodo

MMaya Chen#northwind · 4mOur endpoint was down for a few minutes and retries stopped after three attempts. Can we raise the limit?

SYoujust nowRaised to 12 with backoff, replaying the two missed events now.

Repliesin #northwind-supportasSSam Kowalski

Reply to Maya…⌘↵

Send

# northwind-supportShared channel

MMaya Chen10:42Our endpoint was down for a few minutes and retries stopped after three attempts. Can we raise the limit?

SSam Kowalski10:46Raised to 12 with backoff, replaying the two missed events now.

✅ 1

A customer asks in SlackIn the shared channel they already use.
It lands in one queueNext to email, Teams and Discord.
You answer from WeftWith context, history and a draft.
They see you, not a botYour name and avatar, in their channel.

Works where your customers and engineers already are

Slack
Microsoft Teams
Discord
Telegram
Email
Chat widget
Linear
GitHub
Jira
Notion
PagerDuty
Datadog

Channels

Every channel becomes a thread

Slack Connect, Teams, Discord, email and chat land in one queue. You triage and reply in one place, and the answer goes back where the question was asked.

Explore channels

Inbox

MWebhook retries stop after 3 attemptsSlack ConnectMaya Chen

DSSO login loops on SafariEmailDana Reyes

OCan we export threads to CSV?Discord forumOmar Haddad

Shared channel connectedLive

AI that shows its work

An agent you can audit

The Customer Agent answers with citations, is checked by judges before it sends, and hands off when it is unsure. Backtest it on resolved threads before you switch it on.

Learn about the agent

Customer Agent

DDana ReyesHow do I create a thread through the API? I only have their email address.

Searched knowledge, 2 queries

Drafted a reply from 2 sources

Checked by judgesChecking

API referenceQuickstart

Reply, or hand off to a person…

Hand off

Customer context

Know who is asking before you answer

Every thread opens with the account beside it: plan, revenue, renewal, health, the engineering issue behind it and every earlier conversation. Priority follows what matters.

Explore context

Weft

Webhook retries stop

MMaya ChenCan we raise the retry limit?

Feedback and roadmap

From one problem to what you build next

Promote a thread to a request, weight votes by account revenue, and tell every customer who asked when it ships.

Explore feedback

Feedback

Planned

Export threads to CSV31Hooli +6

In progress

Shipped

12 customers told it shipped

commands customers have to learn

They write in Slack. We ingest it.

queue for every channel

Slack, Teams, Discord, email and chat.

100%

of actions available by API

Parity between app and API, by design.

How it works

From a message to a resolved thread

A customer writes in Slack
In the shared channel they already use. No form, no command, no new tool for them.
Weft turns it into a thread
Grouped by time or by meaning, labelled and prioritised, with the customer and account attached.
Your team answers as themselves
Reply from the queue. It lands in Slack under your own name and avatar, not a bot’s.
The loop closes by itself
Waiting, follow-ups, CSAT and the feature request behind it are handled by workflows.

Principles

Built around a few strong opinions

Customers should never have to learn a command. They write in their own Slack; we do the rest.
No customer-side commands
Replies go out under the agent’s own name and avatar, not a bot account.
Real people, not bots
Every action in the app is an API call, and every API call is available in the app.
API parity
A failed send is a visible, retryable state. Never a silent one.
No silent failures
AI answers cite their sources, are judged before sending, and hand off when unsure.
Honest AI
Bring your own model key. Run it on your own infrastructure if you want to.
Yours to own

What we hold ourselves to

Shipping is the easy part. Trust is the product.

Everything above is in v0. What we obsess over is whether you can rely on it on your worst day.

< 100 ms
to open any thread
From the keyboard, on a bad connection too.
Once
is how often a message is delivered
Exactly once, in order, and never silently dropped.
0
silent failures
A failed send is a visible, retryable state.
14 days
is the most we keep what we don’t need
Delete a message in Slack and we delete it too.

Try Weft now.

Join the private beta. We will reach out as soon as your channel type is ready.