Resources
Use-case library
Find the closest workflow pattern by the problem you are solving, the source that starts the work, or the outcome you need.
Finder
Workflow finder
Work depends on old mailbox history
Work depends on files, attachments, or contracts
Try Due Diligence Document Review, Contract Obligation Monitoring.
Work depends on outside sites changing
Try Site And Portal Monitoring, Third Party Risk Monitoring.
Prompts
Selection prompts
- What starts the work
- Which records are involved
- Who needs the output
- What result the team wants first
01
Browse by what starts the work
Many teams know the trigger before they know the product page they need. Start with the source or event that creates the work.
Inbox backlog or mixed shared mailbox
Use these when work arrives through active mailboxes and the team needs triage, routing, or visibility into what still needs attention.
Mailbox archive or staff handoff
Use these when the problem is historical context, continuity, or lost knowledge after a departure or ownership change.
File-heavy review or mixed documents
Use these when the work depends on attachments, contracts, diligence material, or shared-drive content that should stay tied to the source trail.
External site or portal change
Use these when the source of truth updates on a website or portal and the team needs alerts, review, or a current working view.
02
Browse by the outcome you need
Sometimes the easiest way to choose a page is by the result the team wants.
Triage and routing
Start here when the team needs to sort incoming work, direct it to the right owner, or pass only selected items onward.
Deadline, obligation, or issue tracking
Start here when the team needs to pull dates, statuses, or obligations from communication and supporting documents.
Continuity and handoff
Start here when the team needs usable history after offboarding, reassignment, or a change in ownership.
Secure review and sharing
Start here when another audience needs a controlled view of the result rather than the full working set.
03
Browse by team
Choose the team lens if the problem is already owned by a function.
Operations
Operations teams often start with intake, routing, and exception handling.
Customer support and success
These teams often need fast context lookup and cleaner handoffs.
Sales and account teams
Revenue teams often care about relationship continuity, renewal signals, and obligation visibility.
Finance and procurement
These teams often need date extraction, document context, and monitored external updates.
Legal, compliance, and audit
These teams often care about evidence, review, and traceability.
04
Browse by industry
Use an industry page if sector context matters as much as the workflow itself.
05
How to choose the nearest match
Pick the page that matches the records involved, the trigger that starts the work, and the outcome your team wants first. The page title does not need to match your internal language exactly.
Once you find the closest pattern, move into the related product, security, or solution pages that answer the next question in your evaluation.
Related pages
Go deeper from here
Use the closest product, workflow, or security page to continue the evaluation.
Workflows overview
Browse all workflow pages once you know which family of problem you are dealing with.
Open pageBuyer's guide
Use this next if you are comparing options and need to scope a first rollout.
Open pageImplementation guide
Use this next if you already know which workflow should launch first.
Open pageSolutions overview
See how the same workflow looks from the perspective of different teams.
Open pageIndustries overview
Jump into sector-specific pages when industry context changes the evaluation.
Open pageFAQ
Common questions
What if our use case does not match a page title exactly?
Pick the closest pattern. During evaluation, the workflow can be tailored to the fields, sources, and outputs you actually need.
Why organize this library by workflow instead of feature names?
Because most teams start with a job they need to run, not a feature label they already know.
What should we read after choosing a workflow?
Usually the matching product page, security page, or implementation guide, depending on what question comes next.
Can one workflow lead to others?
Yes. Teams often start with one visible pain point and then expand into adjacent workflows once the first one is live.
Next step
Turn the nearest match into a demo brief
Once you know the closest workflow pattern, it becomes much easier to define scope, access needs, and the first result your team wants to trust.