Intake and routing
Every request sorted and on its way.
Sort deal submissions, claim packets and referral uploads, match them to the right file and route incomplete or unclear documents to a reviewer.
Discuss your use caseChange of address request. Account number 40-118-2207.
- Document type
- Change of address p. 3
- Account
- 40-118-2207 p. 3
- Customer
- Joy Okafor p. 3
What it handles
Everything that arrives, sorted and on its way.
Emails, forms, uploads and scans are split, classified and matched to the right customer, then routed to the team that handles them with the next step ready.
Mixed packets broken into separate documents, each one classified and read for who it is from and what it asks.
Intake DeskEmail from j.okafor@ · 3 attachmentsRoutedExtracted4 fields- Document type
- Change of address p. 3
- Account
- 40-118-2207 p. 3
- Customer
- Joy Okafor p. 3
- Effective
- Nov 1, 2026 p. 3
Checks- Matched to a customer record
- Signature present
- Routed to Account ServicesAddress change workflow started
Open requestRerouteEvery request in one place with its customer, type, urgency and owner, and the ones that could not be matched held for triage.
Ask about any customer and get their open requests, recent letters and history in one answer, each item cited.
How it fits
Every channel in. The right team out.
Strive watches the places requests arrive, works out what each one is, and starts the right workflow for the team that owns it.
Comes in from
- Shared inboxesEmails and their attachments
- Scans and uploadsMailroom scans and portal uploads
- Customer recordsAccounts to match each request to
- 01SplitPackets into separate documents
- 02ClassifyWhat it is and who it is from
- 03RouteBy your rules, to the team that owns it
- 04TriageAnything unclear waits for a person
Goes out to
- A request boardEvery request, its owner and status
- Alerts in SlackUrgent requests to the right channel
- Into your systemsEach request posted where it is worked
What you can do.
Split mixed packets
Scans and attachments broken into separate documents, each one classified.
Match the customer
Every request tied to the right account, with unmatched ones held for triage.
Route by your rules
Requests sent to the team that owns them, with the right workflow started.
See it all in one place
A board of every request, its owner and its status, across every channel.
Apps for this work
Security
Security your IT team will sign off on.
SOC 2 Type II audited controls, encryption everywhere, single sign-on and role-based access. Your data never trains a model.
Security
SOC 2 Type II
Independently audited security controls, tested over time.
Europe
GDPR
Personal data handled under the EU's data protection rules.
California
CCPA
Personal data handled under California's privacy law.
Controls
Encryption
Encryption runs on every layer, built on Google Cloud's security controls. Data is encrypted at rest with keys held in Google Cloud KMS, and every connection is encrypted in transit, including traffic between our own services. The credentials your connections use are encrypted too, and never appear in an app.
- At rest
- AES-256, on Google Cloud.
- Keys
- Held and managed in Google Cloud KMS.
- In transit
- TLS on every connection into the platform.
- Inside the platform
- Traffic between our own services is encrypted too.
- Connection credentials
- Stored encrypted and entered through secure forms. Never shown in apps.
- Exported apps
- Credentials are left out.
No training on your data
Your data is never used to train AI models, and the AI services we use don’t train on it either: we use them on enterprise terms that exclude training. A data processing addendum makes our commitment contractual, and you decide how long your data is kept.
- AI model training
- Your data is never used to train AI models.
- AI services
- Used on enterprise terms, so they don’t train on your data either.
- In writing
- A data processing addendum makes it a contractual commitment.
- Retention
- You decide how long your data is kept.
Single sign-on
People sign in with the identity provider you already use: Google, Microsoft, Okta, or any provider that supports SAML or OpenID Connect. Their groups map to roles in Strive, so the right access follows them in. Systems connect with API keys.
- Providers
- Google, Microsoft, Okta, and any provider that supports SAML or OpenID Connect.
- Protocols
- SAML and OpenID Connect (OIDC).
- Roles
- Groups in your identity provider map to roles in Strive.
- Systems
- API keys.
- Rate limits
- Requests are limited for each organization.
Role-based access
Role-based access control: each person has a role, and the role decides which apps, data and actions they can use. The Assistant works with the same access as the person using it, so it can only see and do what they can.
- Roles
- Assigned to each person, or mapped from groups in your identity provider.
- Apps and data
- A role decides which apps, records and actions a person can use.
- The Assistant
- It has the same access as the person using it, no more.
- Changes it proposes
- They wait for someone with the right role to approve them.
- Actions that cost money
- They ask for confirmation first.
- Organizations
- Each organization's data is kept separate.
Questions
What people ask about intake and routing.
Where can requests come in from?
Gmail, with attachments, and files in OneDrive, Google Drive and other connected storage. Your app can have its own forms and uploads, and your own systems can start a run with a webhook, or over the API.
What happens to a request it can't classify?
It waits in a triage queue for a person, and so does any request it cannot match to a customer. You can also add a review step so the requests your rule picks out wait for a person to approve or edit them before they are routed.
How do we know it sorted a request correctly?
You set the categories, and it can keep the reason for each label it picks, so you can see why a request went where it did. Every field it pulls out points to the exact spot on the page it came from.
What kinds of attachments can it read?
PDF, Word, Excel, CSV, plain text, Markdown, HTML, and PNG, JPEG, TIFF and BMP images. Scanned pages are read with OCR.
Can it open a ticket in the system we already use?
Yes, if that system has a REST API or an MCP server. Connect it, and the workflow posts each routed request there.
Can it hide account numbers and other personal details?
Yes. A redact step masks or removes personal details, like names, numbers and addresses, before anything else sees them.
Which document-heavy job would you hand over first?
Bring one process you want to improve and the information behind it. We build the first version with you in the session, so the first thing you see is your own work, running.
Contact SalesAn hour of your time and a process you know well. That's all it takes.