surehand

The queue gets worked. You still sign.

No IT team needed. We run it for you.

Agents for the shared inbox, the orders, the bills and the follow-ups that pile up with nobody to hand them to. You still sign the calls that matter.

  1. 01rules you sign
  2. 02checked before it acts
  3. 03your approver on hard calls
  4. 04a record that shows any edit
[ what changes ]

You don't need an IT team. You need one person who signs.

The inbox, the late orders, the bills, the follow-ups. All under one page of rules you sign. Every action is checked before it runs. Refunds, payments and anything with a price wait for you. We deploy it and we run it. You keep the record and the say.

[ the queues ]

Four queues. One set of rules.

Pick a queue. What the agent reads and touches, what it may do, where it must stop, and what goes on the record. Then one run of it, simulated.

01 / 04 · Small and mid-size businesses

Shared inbox triage

Classify · Draft from approved answers · Create tickets

Every message sorted. Replies drafted from answers you already approved. Tickets opened. Refunds, complaints and pricing wait for you.

Reads
  • Message
  • Customer record
  • Approved answer set
  • Open tickets
Touches
  • Gmail or Outlook shared inbox
  • HubSpot
  • Help desk
May do
Classify, draft from the approved answer set, open tickets
Stops for
The owner or operations lead, on any refund, complaint or price
On the record
Every message, how it was sorted, every draft, who sent it
fig. 01 · SimulatedRUN-8K1T2 · manifest v1 · shared inbox
  1. READmessage: where is my order 10422?
  2. DRAFTEDdrafted from approved answer shipping-status, tracking attached
  3. READmessage: can I get a discount on a reorder?
  4. HELDpricing: outside manifest, held for owner
  5. READmessage: invoice attached for last month's delivery
  6. PASSfiled to bills queue, ticket opened
  7. SEALEDrecord sealed

DRAFTS FROM APPROVED ANSWERS · PRICES GO TO THE OWNERThree inbox messages: two drafted from approved answers, one held for the owner.

[ your first agent ]

Bring the inbox you dread opening.

Or the late orders, the bills, the follow-ups. Pick one. You sign the rules and clear the calls that stop. We do the rest, and keep running it after launch.

  1. 01

    Study

    One session with you. The queue, the tools, who decides today. You keep the write-up, even if it says not yet.

  2. 02

    Deploy

    We write the rules with you. You sign. The agent works inside the tools you already pay for. Your cloud or ours.

  3. 03

    Run

    You clear the first stopped calls from your phone. We run the agent and tighten the rules as your queue changes.

[ what owners and operations leads bring first ]

Bring the question nobody can answer fast.

  1. 01

    Which messages in the shared inbox can be answered from what we have already approved?

    Queue: Shared inbox triage
  2. 02

    Which orders will be late, and has the customer been told?

    Queue: Order exceptions
  3. 03

    Which bills are due this week, and which have no matching order?

    Queue: Bills and invoices
  4. 04

    Which quotes went quiet, and which renewals are due next month?

    Queue: Follow-ups and renewals
  5. 05

    What did the agent send yesterday, and what did it hold for me?

    Queue: Shared inbox triage
  6. 06

    Which refunds and replacements did I approve this month?

    Queue: Order exceptions
[ Gatehouse ]

You set the rules. It follows them.

Four controls. Your technical team gets the detail on the Gatehouse page.

manifest

The rules, written down once.

Which inbox, which Shopify store, which QuickBooks file, which HubSpot pipeline, and what the agent may do in each. One page, signed by you.

policy check

Checked before it sends or spends.

Every action is checked against the manifest as it happens. A refund over the limit or a message with a new price stops and waits.

approver

You, or the person you name.

Held calls come to one named person with the evidence gathered. Clear them from your phone. Overriding a block takes two names.

sealed record

A record you can read without us.

Each run is chained by SHA-256 and exports in open formats. If we part ways, you keep the record and the rules.

[ security ]

What you can check today.

01

Rules your accountable person signs

Systems, actions, limits and approvers. Written down. Signed before the agent runs.

02

Checked before every action

Every action is checked against your rules as it happens. Not named means refused. The refusal goes on the record.

03

One approver for hard calls

Hard calls wait for one person you name, evidence attached. Overruling a refusal takes two names. Both are saved.

04

A record any edit breaks

Every run is chained by SHA-256. It exports in open formats. Your auditors read it without Gatehouse.

Your cloud or ours. You decide, and the manifest records it.

No SOC 2 report or ISO 27001 certificate today. Your security team gets a walkthrough of the four controls and where the deployment runs. We answer your questionnaire in writing and tell you where certification stands.

Read the security answers
[ composite case ]

One deployment, from queue to record.

Built from more than one engagement. Names and figures changed. No performance figures, because none were measured on a single engagement.

W/03Composite caseInternal operations

Every answer cites its clause. Or a person answers.

The problem

The same easy questions every day. The hard ones waited behind them.

What changed

People only get answers the library backs up. Every correction becomes a worked example.

[ read before you start ]

The questions owners and operations leads ask us first.

Each one answered in full, with its sources. No sign-up to read them.

[ faq ]

Asked before every start.

Not here? Write to support@surehand.io. A person replies, usually inside two business days.

Talk to the people who run it
We have no IT team. Who runs this?

We do. We deploy it and keep running it. You sign the rules and clear the calls that stop. We change the rules only when you sign again.

Where does our data live?

Your cloud or ours. You decide, and the manifest records it. For most small businesses that means the tools you already use, with the agent reading and writing only what the manifest names.

Can it send emails, issue refunds or pay bills on its own?

Only what your rules allow. Drafts from approved answers go out if you say so. Refunds, payments, new prices and anything unnamed wait for you. The check runs before the action, not after.

Do we have to change our tools?

No. The agent works inside the inbox, Shopify, QuickBooks or Xero and HubSpot you already run. Gatehouse sits in front of the agent, not in front of your tools.

What does it cost?

We quote after the teardown, once we know how much comes in and how much goes wrong. Three stages, each quoted. No number on this page is a quote.

What happens if we stop working with Surehand?

You keep the rules, the records and the corrections, in open formats that read without Gatehouse. What happens to the agent itself is in the contract.

Start here

Bring us the queue nobody wants.

Tell us what comes in, who handles it and where it waits. We study it with your team and tell you straight if an agent belongs there. A person replies, usually inside two business days.

support@surehand.io