Setting up and using Ping&Bump

• Slack: @Ping&Bump and your question in a channel an admin has turned on for asking, a direct message to the bot, or /ask anywhere.
• Web: the ask box on /app/[org]. Your questions and the ones you were pinged with are on the same page.
• Your card: /app/[org]/me. What Ping&Bump holds on you in this workspace, who asked about you, and a switch to stop being pinged.
• Unanswered: /app/[org]/gaps, admins. Questions nobody in this workspace could take.

Ping&Bump looks through the work it has read for colleagues who have done this before, and pings the first one who is free. The direct message says who is asking, why this person, and where the answer goes.

They can answer, take it and pick a deadline, say it is not their area, or say they are busy. Anything but an answer sends the question to the next person who fits, up to three. Nobody is told who was asked before them. When nobody fits, the question goes on Unanswered and nobody unqualified is asked instead.

Nobody gets more than two open questions or five pings a day. A ping with no response for four business hours moves on.

We create the workspace and switch it on with you. From there an admin does the rest in the product, on /app/[org]/sources. There is nothing to install and nothing to run.

1. Sign in at pingandbump.com/app with Google, Microsoft, or a one-time email link. One account can belong to several workspaces, so the workspace is always in the address, never guessed from you.
2. Connect Slack first: it is where people ask. Then connect the tools your team works in. Each one has its own tab above and its own Connect button on Sources.
3. Classify what you connected: Citable, Signal-only, or Excluded. Citable can be quoted to anyone in the workspace who could already open the document. Signal-only counts towards a card and is never quoted. Excluded is not read.
4. Turn on the projects, teams, channels or pages Ping&Bump may read, then Save. Nothing inside a source is read until you do this. A source sitting at nothing turned on says so on its own row.
5. Press Read now. The row then says when it was last read, and shows how far through it got. Under the sources, an admin sets how often they are read again. The line under that control is the next read, in the workspace's timezone, and the same sentence is on /app/[org]/council.
6. Admit your colleagues on /app/[org]/people. Use the address they sign in with. They do not need an account yet.

The counter near the top of the sources page, x of y people have a card, is how you know the workspace is ready to be asked something. Nobody without a card is pinged.

Signing in with Google reads nothing from Google Drive. Reading shared drives is its own step, on the Google Drive tab, with an account your company makes for Ping&Bump.

If your company signs in with Microsoft, an admin of your Microsoft tenant approves Ping&Bump once, before anyone else can get in. They press Continue with Microsoft and tick Consent on behalf of your organization. Until then, colleagues are told they need admin approval. Signing in with Microsoft reads nothing from Microsoft 365. Reading SharePoint is its own step, on the Microsoft 365 tab.

SAML and SCIM are not built. Do not plan the rollout around them.

/app/[org]/council is the same information written for somebody who has to approve it. Anyone in the workspace can open it, and it is meant to be handed to a works council rather than summarised for one.

An agent asks as a named person. Mint a key on /app/[org]/agents, then point an MCP client at https://pingandbump.com/api/mcp with Authorization: Bearer …. The key is shown once. Ping&Bump stores a hash.

ask_person, the tool that sends an agent's question to a colleague and brings the answer back, is being built for the pilot and is not on this page until it works. Today the endpoint has:

• who_can_help: a question in, up to three colleagues with evidence out. Nobody fitting is a result, not an error, and goes on Unanswered.
• who_owns: who carries a named capability, and whether exactly one person does. Needs the same admin rights as Unanswered.

There are no scores in any result.

After mint, the Try box on /app/[org]/agents is the zero-setup check. Same function an MCP client calls. A refusal is a result, not an error. It does not ask for a bearer.

MCP Inspector:

npx @modelcontextprotocol/inspector

URL https://pingandbump.com/api/mcp. Header Authorization: Bearer <key>.

Cursor, in mcp.json:

{
  "mcpServers": {
    "pingandbump": {
      "url": "https://pingandbump.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <key>"
      }
    }
  }
}