What teams see
- Work waits between receive lead and fetch company data.
- Owners reconstruct status from Salesforce and Generic REST API.
Sales
Lead qualification and account-fit workflow
Sales representatives spend valuable time manually investigating prospects that do not match the commercial profile.
Business problem
Sales representatives spend valuable time manually investigating prospects that do not match the commercial profile.
Why it happens
- No shared state spans Salesforce, Generic REST API, Microsoft Teams.
- Decision and exception rules are applied inconsistently.
Why it becomes expensive
- Capacity is consumed by coordination and rework.
- Late exceptions weaken visibility and service quality.
Business outcomes
- Shorter qualify in crm cycle
- Fewer handoff and missing-information exceptions
- Clear ownership from receive lead to qualify in crm
- Inspectable decisions and recovery
Measurable KPIs
- Turnaround time: Elapsed time from receive lead to qualify in crm.
- Manual intervention rate: Share of items needing a person outside defined review conditions.
- Exception age: Time unresolved exceptions remain without a completed action.
- Successful completion rate: Share of valid workflow items completing without terminal failure.
How the workflow works
- Receive lead — Accept and identify the lead qualification and account-fit workflow trigger. Salesforce
- Fetch company data — Execute fetch company data with validated sample data and an auditable result. Salesforce
- Validate profile — Execute validate profile with validated sample data and an auditable result. Generic REST API
- Apply fit rules — Execute apply fit rules with validated sample data and an auditable result. Microsoft Teams
- Draft research summary — Execute draft research summary with validated sample data and an auditable result. Salesforce
- Score account — Execute score account with validated sample data and an auditable result. Generic REST API
- Review uncertainty — Execute review uncertainty with validated sample data and an auditable result. SEIDO Review Queue
- Qualify in CRM — Execute qualify in crm with validated sample data and an auditable result. Salesforce
- Audit and KPI update — Persist the execution outcome, audit facts and workflow measurement events. SEIDO execution store
Integrations and ownership
- Salesforce: Provide workflow input
- Generic REST API: Lookup and update context
- Microsoft Teams: Receive controlled outcome
Human responsibility: Revenue operations manager
Failure and recovery
Salesforce is temporarily unavailable.
Retry with capped exponential backoff; preserve the run and move it to the inspectable failure queue after the limit.
Required data for fetch company data is malformed or missing.
Stop downstream actions and show the missing fields, source evidence and correction action to the named reviewer.
The trigger or provider event is delivered more than once.
Return the existing execution identified by the idempotency key and do not repeat downstream business actions.
The human decision expires before completion.
Escalate to the configured substitute, retain the original request and record both expiry and reassignment.
When not to build this
- Monthly volume is too low to justify integrating Salesforce, Generic REST API, Microsoft Teams.
- An existing configured platform already handles lead qualification and account-fit workflow with adequate ownership and reporting.
- Reliable source data or supported API access is unavailable.
- No business owner has authority to define the decision and exception rules.
Related workflows
Intelligent inbound lead routingLeads arrive through disconnected forms, inboxes and campaigns and are assigned too slowly or to the wrong owner.Sales discovery to structured CRMImportant details from discovery calls and notes do not reach the CRM consistently, weakening follow-up and forecasting.Proposal and scope generation workflowSales teams repeatedly copy opportunity data, notes and commercial terms into proposals, creating delay and inconsistency.