Skip to content
neighbot
Get early access

Hey, neighbor.

Neighbot is your friendly support system. Customers get a warm reply in Slack, email or chat, while Neighbot files the issue and checks your Sentry and Datadog for the cause.

Say NAY-bot, like neighbor.

Every connector unlimited for 14 days, with 300 AI reply drafts. No card required.

Slack

Email

Sentry

Datadog

Linear

GitHub

Intake

Signals

Actions

Animation: the neighborhood comes alive. Six houses, your tools, rise onto the street and their windows light one by one. A pulse runs door to door from Slack to GitHub, small notifications pop above the houses, and Neighbot steps out of his door and waves.

How it works

  1. A customer says exports are broken.

    Every report in Slack, email or chat becomes a tracked issue, with an owner and an SLA.

  2. Neighbot knocks next door.

    It checks Sentry and Datadog for that customer. Read-only, nothing new to instrument.

  3. The cause, with receipts.

    A timeout right after release [email protected]. 36 other accounts hit it too.

  4. Engineering gets a ticket, not a thread.

    Linear or GitHub, with the trace, the error and the release attached.

  5. Fixed. Back with support.

    When engineering closes the ticket, the issue comes back to support. You tell the customer.

Slack

Email

Sentry

Datadog

Linear

GitHub

Intake

Signals

Actions

Exports are broken.

Fixed. Back with support.

#4182 · Open

TimeoutError

504 · 30.0s

Likely cause: [email protected]

ENG-2291

Animation: a customer reports "Exports are broken" in Slack. Neighbot checks Sentry and Datadog, finds a timeout after release [email protected], files ENG-2291 in Linear, and when it's fixed the issue comes back to support.

Customers report in Slack. The answer is in Sentry.

B2B customers report problems in shared Slack channels. The evidence for “something broke for me” sits in Sentry and Datadog, but the person answering can't get to it. So reports get lost between channels, support asks for screenshots, and engineering gets pulled in to dig.

Today

  1. Dana posts in the shared Slack channel: “Exports are broken.”
  2. Someone copies it into a ticket and asks for a screenshot.
  3. Support posts in #eng-help. Nobody owns it.
  4. An engineer digs through Datadog and finds the deploy.
  5. Outcome: Northwind has missed month-end close.

With Neighbot

  1. Dana posts in Slack. Neighbot tracks it as issue #4182.
  2. It finds her failed request, the Sentry error and the 09:23 deploy.
  3. Support replies in the thread with the cause and escalates with the evidence attached.
  4. Outcome: Rolled back. Reports from other affected accounts are linked and closed together.

Illustrative example.

Knock knock. It’s Slack.

Connect your shared customer channels and map each one to an account. Every new message from a customer becomes an issue, and the thread becomes the conversation.

  • Each top-level customer message opens an issue; thread replies stay with it.
  • Your replies post back into the customer’s thread as Neighbot, showing your name and avatar.
  • Turn any message into an issue with the message shortcut.
  • If Slack is briefly unavailable, Neighbot retries, so nothing gets lost.
  • Email and the chat widget work the same way: every new email or chat becomes an issue.

Issues that behave like support.

Statuses built for talking to customers, numbers per team, and notes your customer never sees.

  • Per-team issue numbers, like #4182.
  • New, open, waiting on customer, waiting on engineering, on hold, resolved, closed.
  • A customer reply reopens a resolved issue. Resolved issues close after 7 days.
  • Priority, type and tags.
  • Internal notes stay separate from the customer conversation, and every change lands on the timeline.
  1. New
  2. Open
  3. Waiting on customer
  4. Waiting on engineering
  5. On hold
  6. Resolved
  7. Closed auto-close in 7 days

Customer reply reopens it

#4182 CSV export spinning

Example
  • High
  • Bug
  • exports
  • month-end
Conversation Internal notes

Only your team sees this

  1. 09:52Opened from Slack
  2. 09:58Escalated to Linear ENG-2291
  3. 10:20Resolved

Knows everyone on the block, by name.

Every company you support and the people in it, with their issues grouped by account.

  • Accounts with their people and every issue they’ve raised.
  • Customers are matched to their telemetry by email.
  • When an email doesn’t match, set the mapping by hand for that customer.

Every report, with the evidence.

When an issue arrives, Neighbot checks Sentry and Datadog for that customer over the time of the report, and attaches what it finds.

  • Errors, traces and slow endpoints, with links back to the source.
  • Scoped to the customer and the time window of the report.
  • Re-investigate any time with one click.
  • New Relic and PostHog: Coming soon

Engineering gets a ticket, not a thread.

Escalate to Linear or GitHub Issues in one click. The ticket already holds the report, the conversation and the evidence.

  • One click to create the ticket, or link one that already exists.
  • The report, conversation and evidence are written into the ticket.
  • When engineering closes it, the issue comes back to support automatically.
  • Your customer is never messaged without a person on your team sending it.
  • Jira: Coming soon.

Good morning, neighbor.

Neighbot’s home briefing tells you what changed since you were last here and what needs you, with the next step one click away.

  • What happened since your last visit.
  • What stands out, like an error hitting several accounts.
  • What needs you, with one-click next actions.

Since yesterday, 18:40

Example

What happened

  • 7 new issues
  • 4 resolved
  • ENG-2291 closed

What stands out

TimeoutError in ExportJob is hitting 37 accounts

Needs you

  • #4182 Reply to Dana

    Reply
  • #4190 Waiting on engineering for 2 days

    Nudge
  • Kestrel Pay token expired

    Reconnect

Hear what the whole street is asking for.

Feature requests link to the accounts and issues that asked for them, so you can see real demand.

  • Link a request to the issues and accounts behind it.
  • See demand at a glance: how many accounts asked, and which ones.

Feature requests

Example
  • Scheduled CSV exports

    9 accounts

    Northwind Freight, Acme Logistics, +7
  • SSO with Okta

    6 accounts

    Brightline Health, Kestrel Pay, +4
  • Webhook retries

    3 accounts

    Orbit Labs, Kestrel Pay, +1

Lights on at every house.

Neighbot checks its connections and flags a broken token before it costs you a report.

  • Health checks for every connection.
  • Expired or revoked tokens are flagged with a one-click reconnect.

Six houses stand for your connections: Slack, Email, Sentry, Datadog, Linear and GitHub, all with their lights on. Neighbot checks each house in turn. When Datadog's token expires its window goes dark and a Token expired tag appears with a Reconnect button. After the reconnect, the light comes back on.

Your stack is the neighborhood.

Intake brings reports in, signals hold the evidence, actions hand the work to engineering. Signal connections are read-only: nothing new to instrument.

Intake

Where customers report problems.

  • Slack

  • Email

  • Chat

Signals

Where the evidence lives.

  • Sentry

  • Datadog

  • New Relic Coming soon

  • PostHog Coming soon

Actions

Where engineering picks it up.

  • Linear

  • GitHub

  • Jira Coming soon

Matching a customer to their telemetry uses their email, with a manual override per customer.

Use it wherever your customers ask.

Every question lands in one tracker, tied to the customer who asked.

  • Order questions

    Email and chat widget

    “Where’s my order?” and return requests arrive by email or chat. Each one becomes an issue tied to that customer, with their history in one place.

  • Questions on your pricing page

    Chat widget

    Visitors ask before they buy. Your team answers live, or by email if the visitor has already left.

  • Support inside your product

    Chat widget with signed identity

    Signed-in users skip the email step. Their conversations follow them across devices.

  • Bug reports from key accounts

    Slack Connect

    Neighbot checks Sentry or Datadog for that customer and hands the fix to Linear or GitHub. The reply goes back to the same Slack thread.

Answers you can check.

Every reply points to what actually failed: the request, the error and the release. Your team sees the trace, not a guess.

POST /api/exports · 30.0s exports query · 26.2s 0ms 30s
  • Heads of support

    Stop relaying bugs between customers and engineers. Every report is tracked with an owner and an SLA, and answered with the cause.

  • Support engineers

    No more matching emails to user IDs by hand. Neighbot finds the customer in your telemetry and shows what they did and what broke.

  • Engineering leads

    Escalations arrive with the trace, the error group and the deploy attached, instead of “customer says it’s slow.”

Built for B2B software teams that already run Sentry or Datadog.

A good neighbor keeps your keys safe.

Built for teams that let us read their systems.

  • Passwordless sign-in

    Sign in with a code sent to your email. We don't store passwords.

  • Secrets encrypted at rest

    Connector tokens are encrypted before they're stored.

  • Roles

    Owner, admin and member, so the right people manage connections.

  • Private by default

    No customer content goes into our product analytics.

Neighborly pricing.

One plan for the whole team, with unlimited people. Intake is free and unlimited, one signal and one action are included, and you pay only for the extra signals and actions you connect.

The Team plan is $29 a month. Intake is free and unlimited: Slack, email, chat widget and Microsoft Teams. One signal and one action are included, and each extra signal or action is $29 a month.

Team plan

Launch price

Regular price $49 $29 a month for your whole team

  • Unlimited people on your team
  • Intake free and unlimited: Slack, email, chat widget and Microsoft Teams
  • One signal and one action connector included
  • 300 AI reply drafts a month included
  • AI classification unlimited
  • Top up any time: $10 for 2,500 more drafts
  • Customer matching to your telemetry
  • Escalation to Linear and GitHub with the evidence attached
  • Extra signals and actions $29 a month each, no implementation fee
Get early access

Every connector unlimited for 14 days, with 300 AI reply drafts. No card required.

Questions

Is Neighbot a monitoring or alerting tool?

No. Issues start from what your customers report. Neighbot reads the monitoring you already have to find the evidence behind each report.

What does Neighbot connect to?

Slack, email and chat for customer reports, Sentry and Datadog for evidence, and Linear and GitHub for escalations. Microsoft Teams, New Relic, PostHog and Jira are coming later.

Do we need to instrument anything new?

No. Neighbot uses read-only links to the monitoring tools you already pay for.

How long does setup take?

Connect Slack, Sentry and Datadog from Neighbot, then map each shared channel to its account. There's nothing to install in your own code.

How do you handle our data?

Neighbot reads Sentry and Datadog through read-only connections. Connector tokens are encrypted at rest, and no customer content goes into our product analytics.

How much does Neighbot cost?

One Team plan at $29 a month, with unlimited people. Intake connectors are free and unlimited: Slack, email, chat widget and Microsoft Teams. The plan includes one signal (Sentry or Datadog) and one action (Linear or GitHub). Each extra signal or action is $29 a month, and you pay only for the days it is connected.

Are AI reply drafts limited?

Each team gets 300 AI reply drafts a month, trial included. The count resets each billing month, and unused drafts do not carry over. AI classification (suggested type, tags and priority) is unlimited and does not count. On a paid plan you can top up any time: $10 for 2,500 more drafts. Top-up drafts are used after the month's included drafts, and they don't expire while your team has access.

Do we pay for each person on the team?

No. Everyone on your team can sign in to Neighbot at no extra cost. The price follows the tools you connect, not the people who use it.

Is there a yearly plan?

Yes. Pay yearly and get two months free: $290 a year for the Team plan, and the same discount on every extra signal or action.

How does Neighbot find the right customer in our telemetry?

It matches the customer by email. When a customer's email doesn't match what your systems record, you can set the mapping by hand for that customer.

What does engineering get when support escalates?

A Linear or GitHub issue that already holds the trace, the error group and the deploy. Neighbot follows the ticket back to the report.

How does the free trial work?

For 14 days every connector is unlimited and you can add as many people as you like, with 300 AI reply drafts, and no card required. Choose a plan when you are ready.

How do I sign in?

With your work email and a 6-digit code we send you. There are no passwords. New and existing users use the same sign-in page.

What if we don't use Sentry or Datadog yet?

Neighbot works best when your observability is already in place. Without it, there is no evidence for Neighbot to find yet.

How do you say Neighbot?

NAY-bot, like neighbor. A good neighbor has already looked before you knock.

Won’t you be my Neighbot?

Connect Slack and Sentry, and the next customer report arrives with the evidence attached.

Get early access

Every connector unlimited for 14 days, with 300 AI reply drafts. No card required.