Sumora
9 fields evidenced · 46 with no public information. Every value below links to the document it came from and the date we checked it.
5 of those are quoted but not yet interpreted: we hold the source sentence and the date we read it, but nobody has written the answer to the question yet. Those rows show the quote and say so rather than repeating it back as an answer. Why these exist
2 of those are flagged for review: our own check found language in the cited source that may address the field. An editor has not adjudicated them yet.
1 of the evidenced values quotes wording our own later capture of the same page no longer contains. Marked below, awaiting an editor.
Trust gap
How this is scoredAre scope, spend, and authority enforced while the agent runs?
Two distinct enforced controls on the page checked: "Safety limits on every connected account" and a per-campaign authority setting, "Run full auto within your safety limits, or require approval on every send. You can change the setting per campaign." A configurable approval gate is authority enforcement. Short of 3 because the safety limits are never quantified and no spend cap is published.
Judged Aug 16, 2026; evidence newer. We have since re-read Runtime governance, most recently on Sep 3, 2026. No one has re-scored this dimension against it — the score above stands, but it is older than the evidence below it. How current a score is
Is there a tamper-evident record of what it actually did?
No public evidence found. audit_trail is no_public_information. The unified-inbox span previously filed here was downgraded this run: a shared reply inbox is a workflow surface, not a record of agent actions.
How this gap gets closed →Are compliance obligations attached per engagement?
No public evidence found. compliance_certs and regulatory_alignment are both no_public_information against the page checked.
How this gap gets closed →Does payment depend on a verified result?
No public evidence found. Pricing is a flat subscription ("$ 79.99 /mo"); outcome_based_pricing and settlement_mechanism are both no_public_information. Payment does not depend on a booked meeting or any verified result.
How this gap gets closed →Can the deployment be insured, and is the customer indemnified?
No public evidence found. insurance_available, insurance_carriers, indemnification and liability_cap are all no_public_information against the page checked.
How this gap gets closed →Assurance
- Insurance available
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Insurance carriers
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Coverage limits
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Indemnification
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Liability cap
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Audit trail
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Tamper-evident log
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Explainability
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Runtime governance
- Paces outreach to respect each platform's activity limits and warms accounts gradually; nothing sends without passing the customer's approval controls.
“Sumora respects each platform's activity limits, warms accounts gradually, and paces outreach like a careful human would.”
trysumora.com · checked Sep 3, 2026 - Permission scopes
“Run full auto within your safety limits, or require approval on every send. You can change the setting per campaign.”
trysumora.com · checked Aug 11, 2026- Compliance certifications
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Regulatory alignment
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Outcome-based pricing
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Settlement mechanism
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Dispute process
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- SLA terms
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Evaluation coverage
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
Agency
- Autonomy level
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Human oversight
- no public information
Flagged for review — the source below contains language that may address this field. Not yet checked by an editor. How we check absences
trysumora.com · checked Aug 11, 2026 - Goal complexity
“Sumora runs multi-touch sequences that keep qualified leads warm until they're ready to talk”
trysumora.com · checked Aug 11, 2026- Action space
- Autonomous outreach agent that finds leads, sends personalized outreach, warms prospects over a sequence, and drafts replies for the operator to approve.
“Sumora finds matching leads, sends personalized outreach, warms each prospect over a sequence, and drafts every reply.”
trysumora.com · checked Sep 3, 2026 - Operating environment
“Connect LinkedIn and Instagram”
trysumora.com · checked Aug 11, 2026- Initiative
- Described in FAQ as an autonomous outreach agent operating continuously once connected; homepage copy has shifted toward a done-for-you managed-service framing rather than the prior self-serve 24/7 language.
“Sumora is an autonomous outreach agent.”
trysumora.com · checked Sep 3, 2026
Safety
- Safety evaluations
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Red teaming
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Safety policy
“Sumora respects each platform's activity limits, warms accounts gradually, and paces outreach like a careful human would.”
trysumora.com · checked Aug 11, 2026- Usage restrictions
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Model or system card
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Incident reporting
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Third-party evaluations
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Data handling
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
Practicality
- Pricing model
- Plans are paid upfront with no usage-based billing described, and can be cancelled anytime; the homepage no longer publishes a self-serve price and instead pushes toward a sales call.
“Every plan is paid upfront and you can cancel any plan whenever you like.”
trysumora.com · checked Sep 3, 2026 - Price point
- no public informationtrysumora.com · checked Sep 3, 2026 · source did not state this
- Availability
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Deployment options
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Integrations
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Supported regions
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Support model
- no public informationtrysumora.com · checked Sep 3, 2026 · source did not state this
Foundation models
- Base models
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Model provider
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Model swappable
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Open weights
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Fine-tuning
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Context window
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
Ecosystem
- Protocols supported
- no public informationtrysumora.com · checked Sep 3, 2026 · source did not state this
- Tool use
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Multi-agent
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- API access
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Open source
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Marketplace presence
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
Impact
- User base
- no public information
Flagged for review — the source below contains language that may address this field. Not yet checked by an editor. How we check absences
trysumora.com · checked Aug 11, 2026 - Deployment scale
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Target sectors
“Founders and heads of growth at B2B SaaS”
Not in our latest capture. This quote was on the page when we filed it. We captured the same page again on Sep 10, 2026 and it was not there. The value above has not been re-checked by an editor yet. How we re-check citations
trysumora.com · checked Aug 11, 2026- High-risk domains
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this
- Documented incidents
- no public informationtrysumora.com · checked Aug 11, 2026 · source did not state this