Twenty-seven jobs. One system. One login.

• –One line of script, on every product you run
• –Who is on the site now, by country or state
• –A limit your team can tighten for each product, and nothing can raise

Worth knowingIn the US a visit can be claimed as a person — on evidence they volunteered, through Runner's own naming on AI included, or through an identity provider you connect yourself, on your own key — and a teammate approves it before it becomes a contact. In Australia, Canada, the EU, Japan, Korea and the UK the same is possible only for a visitor who turned Recognition on in the site's notice themselves. Everywhere else you get the company, or just the count.

• –One update reaches every site through the embed already in place
• –A scheduled check of each listed site's main address, with a review queue for what is running but not declared
• –A preference centre visitors can return to
• –Every choice kept with the version they saw

Worth knowingThe scheduled check reads a site's markup and headers on a few pages, so a tag a tag manager adds while the page runs is governed once you declare it, and only the sites you list are checked.

• –Accounts, contacts and opportunities
• –Owners, next actions and notes
• –Stage history, and for contacts from a connected system, the record they came from

Worth knowingReady-made record types and pipeline stages make Runner useful on day one — a place to keep the record, rather than a platform you have to build first.

• –Runner reads a company's own website and keeps what it says, with the source
• –Every claim lands with its source and the time it was read
• –A fit scorecard your team fills in, with the evidence behind each score

Worth knowingRunner does the reading on a research account you connect yourself, then files the evidence for your team to review. What comes back is evidence for a decision — never permission to contact anyone.

• –Lifecycle, consent, geography, recency and delivery history, from a set list
• –An estimated size before you commit to it
• –Per contact, the reason they matched
• –Your GA4 page-visit audiences, brought in as segments

Worth knowingConditions come from a set list, in plain language, one condition per phrase — a phrase it does not recognise comes back to you.

• –One teammate gives the go-ahead before anything goes out
• –Sending windows, pacing and a daily cap on each mailbox
• –Opt-outs and bounces handled for you
• –Timed multi-step follow-up, in the journey engine

Worth knowingLive sending ships off for your organization and for each product, and an admin turns each one on, so your team chooses when automation begins. A platform switch sits above both, and while any of the three is off no campaign email leaves.

• –Hosted booking pages on the hours you set
• –A personal booking page for every teammate
• –Slot holds, timezones and daily limits
• –A team rota: by turn, by who has waited longest, or a time everyone is free
• –One script tag puts the booking inside your own page
• –Each booking kept as a meeting

Worth knowingA rota shares bookings out by countable rules — each member in turn, whoever has waited longest, or a time everyone on it is free. Weighting one person's share, or ranking the team by past performance, sits outside it.

• –A hosted form page, or your own site's form posting to Runner
• –Spam guards, and a list of the domains allowed to post
• –Consent recorded only when asked for, ticked and current, with the exact wording kept
• –A question that opens or hides based on an earlier answer
• –Answers a question was never put to are counted apart from answers left blank
• –A thank-you email and a team alert on every form, each step's result on one page
• –An owner for each submission, by a rule on one answer or in turn
• –A quiz that sorts each answer into a result you write

Worth knowingA rule shows or hides a later question from one earlier answer, and a quiz scores answers into the results you write. The thank-you is a receipt from your product's own sender, once one is set up; past that, each form hands the new lead to the email, chat or calling workflow your team chooses for follow-up.

• –One script tag, limited by default to the domains you list
• –It tells every visitor it is an AI
• –One tap asks for a person, and once a teammate takes over the AI stops replying

Worth knowingIt arrives switched off until you turn it on. When a pricing, legal, security or similar answer has no source, or the model isn't confident, it says a teammate will follow up rather than guessing, and no audio from a site visitor ever reaches Runner.

• –Plans and creates your GA4 property in your own Google account, then reads the setup back to check it
• –Reconciles it against your own first-party events
• –Holdout groups on the audiences you build

Worth knowingEvery number here is worked out from data you already hold — your own events, rather than a tracking script watching the rest of your tools.

• –Branded short links that count their clicks, with link-preview crawlers left out
• –A partner portal showing each partner their programs and codes
• –Commissions with hold periods and disputes

Worth knowingRunner works out what each partner is owed from the orders your team records. The money moves through whatever you already pay people with — never through Runner.

• –Duplicate pairs, each with the reasons it was flagged
• –Where both contacts sat on the same product, the more protective email, call and recording consent is kept
• –Each merge records the rows it moved, so undo can put them back

Worth knowingRunner brings each likely pair to a person — one reviewed pair at a time, never in bulk on a schedule. A contact undo puts the moved rows back unless one has changed since, and what was combined into the kept contact — consent, and a membership, tag, property or link both held — stays with it. An account undo moves its contacts, opportunities and evidence back as they are now.

• –Sends wait for a go-ahead from an owner or admin
• –Whoever prepared a send is refused as its approver, outside a one-person team or a time-boxed exception
• –Delegation for a set period, never beyond the delegator's own authority
• –One page listing decisions from several areas, with who decided and when
• –Every approval and rejection kept in an audit trail nothing in the product can edit or delete

Worth knowingThe decision history records what was decided; it never decides. Every approval comes from a person: on the page that owns the work, or through a rule an owner or admin saved for one kind of work, within a weekly limit. The few entries made automatically, such as whether a meeting was recorded, are marked automatic, and each entry links back.

• –An MCP endpoint your agent connects to, with OAuth
• –Permissions checked fresh on every call, never from a cached copy
• –Every tool is graded, and a public post from anyone but an owner or admin waits in Approvals
• –Each answer checked against the shape its tool declares before it goes back
• –A stop control for the workspace, a project, one tool or one person's connections

Worth knowingWhat an agent may call follows the permissions of the teammate it signed in as, checked again on every call, and destructive work stays off the list by design. A tool that changes a record declares the approval it needs and how it is undone; a public post runs on an owner's or admin's own call and waits in Approvals for anyone else's — these are the controls around an agent, not an agent deciding for you.

• –Discord, Telegram and your chat widget in one record
• –SLA tracking and next-action ownership per conversation
• –Human handoff from any channel

Worth knowingThe inbox gathers Discord, Telegram and your chat widget; messages on other channels stay in their own apps, and nothing from LinkedIn messages is read or kept.

• –Every stage counted against one denominator, not five different ones
• –Open any stage and see the deals inside it, with their accounts
• –Outcomes recorded when a deal closes, win or lose

Worth knowingThe counts use six fixed stages and the deals your team records: no predicted close dates and no win probabilities, which is exactly why the numbers reconcile. An inbound lead can carry one labelled suggestion beside it — Runner's reading of a named, versioned qualification policy, with its reasons shown — and that suggestion never moves a stage, a count or a total.

• –Contacts with their email consent and opt-outs, in one versioned export
• –Where each contact came from, carried with it
• –A read-only snapshot that leaves the live record untouched

Worth knowingOne export covers one product's contacts, read in a single request — check its row count against your directory — each carrying the email consent state already on its record — including unknown where no basis was recorded — and any opt-out. Permission for calls and for each messaging channel is kept separately and stays out of the file.

• –A lead for each channel, writing only for its own
• –A weekly review: more of the goal for the lead that brought in the most, once you approve
• –An ad budget split proposed from results, for you to approve
• –A daily update of what each member did, added up from recorded decisions

Worth knowingDaily limits start at zero, so nothing goes out on its own until you raise them, switching the team on asks you to confirm it's you, and every result it shows comes from a record.

• –One calendar showing what waits for you, what's approved and what's scheduled
• –An open slot drafts a post in one press
• –LinkedIn posts go out from your company Page, never your personal profile
• –Connecting posts nothing, and each post waits for your OK unless you let a team member that has earned it post on its own

Worth knowingRunner publishes directly to LinkedIn Pages, Instagram, Facebook Pages and Bluesky; on X and Reddit it opens the post with the words in, and you press send.

• –Pictures and short video clips for every ad, from one brief
• –Every change shows its before and after, and what it does to spend
• –A change applies once approved, or when it fits a budget you approved
• –The team proposes each channel's share from results, and you approve it

Worth knowingThe managed budget comes with Team and above: inside it Runner sets daily budgets and pauses campaigns, and a person approves every new campaign and every raise to the budget.

• –Every search you appear for, with its position and 28-day move
• –History back to the 16 months Google serves, then every day kept
• –Each search beside the revenue of the page that ranked
• –A tracked list picked from real searches

Worth knowingPositions are Search Console's own figures for your site, averaged over the searches it reports, and revenue belongs to the page that ranked, never split onto a keyword.

• –ChatGPT, Claude and Gemini, asked what a buyer asks
• –Three fixes, drawn from the answers that left you out
• –Note the one change you made, and the next check reads against it
• –Every check kept, with its date

Worth knowingAn owner or admin runs a check, at most once a day for each product, and it shows what each assistant answered that day.

• –One private link: their team in a browser, their agent with the same link
• –Every answer shows the record it came from, and a held fact waits for its owner
• –A plan both sides work from, every tick on the record
• –Sign in the room: draw, type or use your saved signature, and both sides get the signed PDF

Worth knowingA person on your side approves the terms, and only the named signers sign, never an agent. Electronic signatures are recognised for most commercial agreements under the US ESIGN Act and UETA and Korea's Electronic Signatures Act. Some documents, such as wills, family-law matters and personal guarantees, still need paper.

• –The sidebar, your list and setup in your word: stores, boutiques, locations or brands
• –Hand a store over with a work email and a job title
• –Every store grouped by region, with who runs it and whether its team is at work
• –One line: teams at work, invites waiting, stores still to hand off

Worth knowingEach store or brand is one product on your plan, and each person you hand one to uses a seat; your owners and admins see every store, and each manager sees their own.

• –How many stopped at each display, and for how long
• –Zones you draw on a still that stays on your computer
• –The week's results on a page of their own

Worth knowingRunner receives one row per display every 15 minutes — how many stopped, how long, and whether the look was positive, neutral or negative — no video, no faces and no identities ever leave the store. Not available to businesses or stores in Illinois, Texas or Washington.

• –A US number your agents answer, on every call or when nobody picks up
• –They recognize each customer, by call or email
• –A caller can ask for a person at any time
• –Email lands in Runner; they draft the reply, you press Send

Worth knowingAgent phone line and Agent email are added to a plan that includes AI, and every call your agents place and every email they draft waits for your OK, with your do-not-contact list always winning.

• –A reply drafted for each review, in its own language and your own voice
• –A daily check of your Google reviews, with an alert in the app, by email and by push
• –Your review link, a QR code, a counter card and a draft email to customers who said yes
• –With two or more locations, one line each: stars, trend, share answered, time to answer

Worth knowingReviews is added for each location, and you post every reply yourself: one tap copies it and opens the review on Google, so nothing goes out without you. The daily check reads the reviews Google shows, and a review about health, a legal matter or safety gets no draft and is marked for you to answer personally.