Why do reputation agencies fear a gating complaint?
A gating complaint starts when the collect page asks how the visit went, then only the happy path sees Google or Facebook. The angry path sees a form. Platforms have seen that pattern. Clients have been banned for it. Agencies inherit the screenshot.
The second fear is a one-pillar tool. You win the review inbox and still cannot find the next account, cannot prove a listing leak, cannot attach a DEMO site or an inbound line, cannot run the client after the close. Climbo and Birdeye are good at the inbox. They stop there on purpose.
Nerxus One is insurance against both. Echo cannot hide public buttons. Private recovery sits alongside. Scout still hunts. Radar still diagnoses a thin count, a rating drop, an unclaimed listing. Forge still builds. Relay still sends a specific sentence. Steward still takes the win. Nova routes those jobs. Scout never contacts from the search screen. Yelp and Tripadvisor stay monitor or assisted until live reply is real. Overnight collection is not a production claim. Health stays a band the owner never sees.
You remain the marketer. The restaurant, the dentist, and the shop are customers. They see a portal and a collect page. They do not see a switch labeled gate. Write the lock into the MSA. Show the page in the kickoff. If they ask to hide Google, the answer is no, and the product will not do it if you waffle.
What does Nerxus One do for a review or reputation firm?
It lets you find businesses whose public ratings and listing hygiene are already a problem, prove the problem, collect without gating, reply in draft, and keep the rest of growth work in the same tenant. Echo is the specialist. It is not the whole company.
Find tags low rating, few reviews, unclaimed listing, and later Watchtower diffs. Prove puts modeled dollars on chair-hour or no-show only when the vertical model exists, and always with assumptions. Win sends a collect DEMO or a reputation memo, not a generic "we manage reviews" blast.
Build is the collect page, the showcase, the campaign, and whatever else the diagnostic leftover named: a site, a service page, inbound voice. Run is Steward plus the portal so month two is leftover findings, not a new login.
If you only ever want the inbox, you will be happier in a reputation suite. This page is for the firm that got tired of handing the website and the SEO to someone else after the review close.
How does Echo collect reviews without a gating branch?
The collect page renders public review buttons for every visitor. The sentiment question, if you use one, does not decide whether Google appears. Private recovery is a parallel path for people who want to talk to the business. Parallel is the word. Instead-of is the banned word, and the UI cannot do it.
Campaigns request a review from people who already have a relationship you can defend: first-party lists, form consents, customers who opted in. There is no Scout-to-SMS hop. Cold SMS is locked on the Autonomy Matrix. Forms cannot pre-check marketing consent.
Replies are drafts. You post, or a connection posts, when the credential is real. Do not claim live Google, Facebook, or Trustpilot replies until those are exercised. Yelp and Tripadvisor are monitor or assisted. Sentiment is a label to triage, not a score you invent for a pitch deck.
Showcase can sit on a page Forge builds. It still cannot become a filter that only displays five stars while the collect page hides the rest. The lock is the product.
Which detectors should a reputation shop hunt first?
Low rating, thin review count, unclaimed listing, and a missing collect path. Those are cheap, visible, and fulfillable this week. A dropping rating on Watchtower is timing. Timing is a better Wednesday mail than "we noticed you have a Google page."
Pair reputation with the vertical trigger when you sell into a pack. Dental: empty chair plus a listing that cannot book. Restaurants: menu AEO plus an unanswered phone plus the review pile. Auto: a two-star week and a bay that should have been booked. Home services: thin GBP after a storm.
Do not hunt "quality businesses." Hunt a metro and a rating problem you can fulfill. ICP stores that hunt. LeadScore ranks sellability from cheap tags. It does not forecast how nice the owner will be on a call.
License drift and ADA can appear on the same row. They are other conversations. Sell them if you fulfill them. Do not bury a gating-safe collect pitch inside a twelve-finding dump the owner cannot read.
What does Monday look like when the board is named after a rating drop?
Monday Scout runs the ICP. You save rows with a rating or count tag you can work. Pulse gets a board like Two-Star Auto or Thin-Review Dentists. You do not export to a shared agency inbox that also holds another brand's locations.
You do not email from the search screen. Scout is read-only. The junior who used to paste stars into Mailchimp will feel slowed down. That pause is how you avoid a blast that looks like a purchased list.
Watchtower schedules the re-scan. A shop that was a 4.4 and is now a 3.9 is a finding. A shop that gained forty reviews because they gated is not a success story you should copy. We will not help you copy it.
If Yelp is connected, it deepens a slice. If it is not, the source is unknown. Do not color the row green.
What does Wednesday look like when the DEMO is a collect page?
Wednesday Radar deep-diagnoses the accounts you would take. Atlas brands the memo. Modeled dollars, if present, keep their assumptions. A thin review count is not a license to invent monthly revenue.
Forge or Echo opens the collect DEMO from the fulfillment action. You send the live link. The sentence is: your listing is thin and dropping, I already built a collect page that does not hide Google, here it is. Sample-first still applies when the sample is not a website.
Relay stays Supervised. Stop-on-reply stays on. You are not Instantly. A reputation firm that needs inbox rotation at volume should keep Instantly for that job and keep us for the finding plus the page.
If they already pay Climbo, you are selling the rest of the loop or a collect page they can defend. You are not required to rip the inbox out on day one. Honesty about the stack retains better than a migration speech.
What does Friday look like when the retainer is collection plus leftovers?
Friday Steward holds the client. Leftover findings become the site they still need, the service page Google cannot read, or the inbound line that stops the missed-call review. Health is a band. The portal shows counts and work in plain language. It does not show your internal "this owner is difficult" note.
Echo keeps drafting replies. You keep posting. Campaigns stay first-party. If they want SMS reminders, Forms is the birthplace of that list. There is no purchased-list import that becomes texts.
Muse can support a month of reputation-adjacent content if you sell it. Publish is gated. A reply is not a blog post. Do not let a model auto-answer a medical or legal review as if it were a burger complaint. Vertical pages say where we stop.
Renewals should attach to leftover work. A review-only retainer that never touches the listing or the site will feel like every other reputation bill. The loop is how you stop being interchangeable. You can fulfill only Echo in month one. When a leftover is a missing site, you partner, hire, or open Forge. DEMO then DEPLOY. Approval is the job.
Which compliance lock matters most to a reputation agency?
The collect-page lock. Say it in the kickoff. Show the page. If a client asks you to hide Google from unhappy visitors, the answer is no, and the product will not do it if you waffle.
Cold SMS and cold voice are next. Review requests that text a scraped phone list are how reputation firms become the story. Locked. Forms only.
The sending domain still matters because outreach is how you sold the work. Unverified is a block. Gating-safe collection does not excuse a burned domain.
We do not claim HIPAA on medical reviews. We are not an EHR. Read the medical industry page before you pitch a clinic a "compliant reputation OS." Drafts and professional review recommended apply to privacy copy the same way they apply to ADA.
How should a reputation shop use sequences without sounding like a blast?
Start from the detector. Thin count, rating drop, unclaimed listing. The mail names the listing and the DEMO. It does not say "we help businesses get more five-star reviews" to two hundred rows.
Stop on reply. Classify. A question is not a green light to enroll them in a six-step education sequence about review psychology. The inbox is the product after they speak.
Professional services want trust pages and AEO more than a blast. Dental wants the chair and the book button. Restaurants want the menu and the phone. Match the industry trigger. A reputation sequence that ignores the vertical reads like a blast even when it is one-to-one.
Atlas can attach the memo. A screenshot of their rating trend, if Watchtower has it, beats a stock photo of stars. We will not invent a case study owner named Maria who gained 140 reviews.
When should you stay on Climbo or Birdeye and skip this product?
Stay when reviews are the only SKU, procurement wants an enterprise reputation platform, and nobody is asking you to find the next logo or build a site. Birdeye wins that bake-off. Climbo wins a reputation-first depth bake-off.
Add us when the close keeps dying because you cannot show a DEMO, cannot diagnose the listing beyond stars, or cannot keep the account without standing up five other tools.
We will not claim more locations, more networks, or more SLA chrome than an enterprise suite. We claim a collect page that cannot gate, plus the loop.
GoHighLevel may still sit after the client exists if your funnels live there. Steward is not a promise to empty that CRM next quarter.
What should a reputation agency refuse to put in a proposal this month?
Refuse guaranteed star ratings. Refuse "we filter unhappy customers." Refuse live Yelp replies if the connection is assisted. Refuse overnight autonomous campaigns that already ran in production if the runner is the open half.
Refuse a price you invent for Nerxus on the proposal. Our commercial policy is unpublished. Your fee is yours. DEV is modeled for the SMB and is not your invoice.
Refuse mixing two locations from two clients on one collect campaign to save a click. Isolation is the agency fear and it applies to review URLs as much as to senders.
Refuse medical or legal reply automation that pretends the model is a clinician or a lawyer. Echo drafts. A human who understands the vertical posts.
How does a reputation firm run Find through Run without becoming a web studio overnight?
You can fulfill only Echo in month one. The loop still sits there. When a diagnostic leftover is a missing site, you either partner, hire, or open Forge. The product will not force you to become a designer on Tuesday.
Nova can route a reputation-only instruction. "Find cafes in one metro with a rating under a threshold and no collect path" is Scout plus detectors. You still choose what to build.
If you never open Forge, you will look like a one-pillar tool that happens to hunt. That is allowed. The fear this page named was gating and the dead end after the inbox. Hunting without gating already changes the week.
When you do open Forge, DEMO then DEPLOY. Do not publish a showcase site because the model was sure. Approval is the job.
How should Echo sit next to Atlas so the memo does not become a star chart?
Atlas can brand a reputation memo with evidence: count, rating, a Watchtower drop, a screenshot of the listing. The credibility gate still refuses a bare dollar. "This shop is losing twelve thousand a month in reputation" without assumptions is the same lie as an unearned chair-hour number.
Echo then attaches the collect DEMO. The meeting is the listing plus the page that cannot gate. A slide of industry averages with no source is weasel attribution. We will not print one, and you should not tape one to our memo.
If you already export charts from Climbo or Birdeye, bring them as their artifact. Do not launder them into an Atlas cover that implies we measured their networks. Unknown sources stay unlabeled as live.
Sentiment labels triage the inbox. They are not a personality score you sell to a franchise. A "negative" tag on a review about a wait time is a queue, not a diagnosis of the owner.
What happens when a client asks you to hide Google after a two-star week?
You say no, and you show the collect page. The public buttons are there for the next visitor too. Private recovery is the path for the person who wants to talk to the manager. Alongside is allowed. Instead-of is the complaint.
Watchtower can still treat the drop as timing. Relay can still send a specific sentence to a prospect who looks like them, or a leftover-finding note to the client who already pays you. None of that requires a filter.
If they fire you for the no, you lost a client who was going to make you famous in a platform ticket. If they stay, Steward keeps the leftovers: the site, the phone, the unlisted service. A two-star week is often a callback problem. Voice inbound and a quote widget are fulfillment, not a cover-up.
Document the lock in the MSA in language a human can read. The product will not grow a toggle later because a QBR was awkward. The Autonomy Matrix already painted that row red.
How should a reputation shop use Watchtower without turning a drop into a blast?
A rating drop on a saved row is timing. It can become a leftover note to a client you already have, or a specific mail to a prospect who looks like them. It cannot become a metro-wide sequence that says we noticed your stars.
Freshness clocks should match how fast reviews move. A restaurant drop is faster than a law firm's. Pulse should show the clock. Re-scraping the whole city because one cafe slipped is theater.
If the drop followed a gated funnel they ran before they met you, do not copy the funnel to "fix" it. Show the collect page that cannot hide Google. The lock is the pitch.
Yelp diffs stay unknown or assisted until the connection is real. A Watchtower tile that implies live Yelp depth you do not have is a green check from nowhere.
How do you staff Echo replies when two verticals share one inbox?
Split Pulse boards and reply guides by vertical. A burger complaint and a medical wait-time review do not share a tone. The medical page already said auto-reply is how you get famous in the wrong way. A reputation shop that ignores that because the inbox is one product will learn it in a screenshot.
Drafts stay drafts. A named human posts. If you cannot staff that human for clinics or firms, do not sell those books. The loop will still hunt restaurants and shops you can answer.
How do reputation agencies join the waitlist without a public price?
Say you sell reputation, which verticals, and whether you already operate a collect page you can defend. Access opens in batches.
Read the collection guide while you wait. It is useful if you never buy. Public buttons. Private recovery alongside. No purchased-list texts.
When a seat opens, connect the sources you actually have, write an ICP around a rating problem, save a signal-named board, build one collect DEMO, verify a domain, send one Supervised sequence. Show the lock in the first meeting so the client cannot ask you to gate later and claim surprise.
If isolation is the louder fear, read Agencies. If you sell AI workshops that die after the review demo, read AI consultants. Same roster. Different complaint.
How do you write the collect lock into an MSA?
You write the collect lock into an MSA in language a human can read: public review buttons stay visible to every visitor, private recovery may sit alongside, and there is no hide-the-buttons branch. The product will not grow a toggle later because a QBR was awkward. The Autonomy Matrix already painted that row red.
If they fire you for the no, you lost a client who was going to make you famous in a platform ticket. If they stay, Steward keeps the leftovers: the site, the phone, the unlisted service. A two-star week is often a callback problem. Voice inbound and a quote widget are fulfillment, not a cover-up.
Show the page in the kickoff. If a client asks you to hide Google from unhappy visitors, the answer is no, and the product will not do it if you waffle. Cold SMS and cold voice are next in the same exhibit. Review requests that text a scraped phone list are how reputation firms become the story.
We do not claim HIPAA on medical reviews. We are not an EHR. Read the medical industry page before you pitch a clinic a compliant reputation OS. Drafts and professional review recommended apply to privacy copy the same way they apply to ADA.
What does a first-party campaign look like after they pay?
A first-party campaign after they pay looks like a collect page and a request to people who already have a relationship you can defend: form consents, customers who opted in, a thank-you mail they already send. There is no Scout-to-SMS hop. Cold SMS is locked. Forms cannot pre-check marketing consent.
Friday Steward holds the client. Echo keeps drafting replies. You keep posting. If they want SMS reminders, Forms is the birthplace of that list. There is no purchased-list import that becomes texts. Campaigns wait until they ask if the opening motion was a listing DEMO.
Stop on reply if you used Relay to sell the work. A question is not a green light to enroll them in a six-step education sequence about review psychology. The inbox is the product after they speak. Professional services want trust pages more than a blast. Match the industry trigger.
Showcase can sit on a page Forge builds. It still cannot become a filter that only displays five stars while the collect page hides the rest. The lock is the product. Yelp and Tripadvisor stay monitor or assisted. Do not imply a live reply they cannot tap.
How should a reputation shop use leftover site findings?
A reputation shop should use leftover site findings by treating them as month-two work on Steward, not as a requirement to become a designer on Tuesday. You can fulfill only Echo in month one. When a diagnostic leftover is a missing site, you either partner, hire, or open Forge.
Nova can route a reputation-only instruction. Find cafes in one metro with a rating under a threshold and no collect path is Scout plus detectors. You still choose what to build. If you never open Forge, you will look like a one-pillar tool that happens to hunt. That is allowed.
When you do open Forge, DEMO then DEPLOY. Do not publish a showcase site because the model was sure. Approval is the job. A launch-only collect month that never touches the listing or the phone will feel like every other reputation bill at renewal.
The loop is how you stop being interchangeable. Hunting without gating already changes the week. The fear this page named was a gating complaint and the dead end after the inbox.
What does assisted Yelp mean in a QBR?
Assisted Yelp in a QBR means you copy and paste with a draft, not that Echo posted there from this product. Monitor means you can see. Live reply requires credentials that have been exercised. Until then, say unknown or assisted. Do not color the row green.
If you already export charts from Climbo or Birdeye, bring them as their artifact. Do not launder them into an Atlas cover that implies we measured their networks. Unknown sources stay unlabeled as live. Sentiment labels triage the inbox. They are not a personality score you sell to a franchise.
Atlas can brand a reputation memo with evidence: count, rating, a Watchtower drop, a screenshot of the listing. The credibility gate still refuses a bare dollar. This shop is losing twelve thousand a month in reputation without assumptions is the same lie as an unearned chair-hour number.
A slide of industry averages with no source is weasel attribution. We will not print one, and you should not tape one to our memo. Google and Facebook follow the connections you actually have. Trustpilot the same.
How do you keep two locations from sharing a collect URL?
You keep two locations from sharing a collect URL by giving each business row its own page and its own campaign. Isolation is the agency fear and it applies to review URLs as much as to senders. Collapsing two shops to save a click is how downtown sees the suburb's one-star week.
Portals stay one business. A group manager can hold two magic links. They cannot hold a merged collect token that leaks reviews. v1 will not give the group a sub-account factory. If they demand chrome-resale, the agency size page already said Not doing.
Pulse boards should be signal-named per book. Two-Star Auto for one rooftop is a campaign. All locations is a scrap pile. Watchtower diffs per row. A drop at one bay is not a success story you blast to the other eleven.
Staff Echo replies by vertical if two trades share one inbox. A burger complaint and a medical wait-time review do not share a tone. Drafts stay drafts. A named human posts. If you cannot staff that human for clinics, do not sell those books. Public buttons stay public. Assisted sources stay labeled assisted. Overnight collection is not a production claim.