Every visit ends in a recorded outcome and a clear next action
Carry what happened at the customer's site into the customer record and the manager's view, with less repeated reporting and fewer calls chasing updates.
Built on
- Field Sales (iField)Controlled beta
- iConnect CRMControlled rollout
- Leads & Sales (iSales)Controlled rollout
Does this sound familiar?
Representatives visit customers all week. Outcomes are reported later by phone or chat, details get lost, and the manager hears about a promised follow-up only when the customer calls to ask about it.
Who is involved
- Field representative
- Field or sales manager
- Salesperson who owns the account
From trigger to outcome
Follow the work from the first trigger. Each arrow names what passes along it and carries its evidence status in words, so a planned step never looks like a working one.
How to read the lines
- Solid line: Demonstrated in testing
- Dashed line: Planned
| From | To | What passes | Evidence |
|---|---|---|---|
| From:iField | To:CRM | What passes:Visit outcome + next action | Demonstrated in testing |
| From:iField | To:Manager | What passes:Completed-visit notice | Demonstrated in testing |
| From:iField | To:iSales | What passes:Visit outcome opens or moves a deal | Planned |
Who acts at each hand-off
The people involved, in the order the work passes between them.
Field representative
Checks in at the customer, then records the visit outcome and the next action
Result: A visit outcome with a due follow-up on the customer's timeline
Next owner: Manager
Manager
Receives the completed-visit notice and reviews outcomes that need action
Result: Follow-ups confirmed or reassigned
Next owner: Salesperson
Salesperson
Opens the customer record before the next contact and updates the deal where the visit changed it
Result: A deal stage that reflects what happened at the visit
Next owner: Sales manager
What each product contributes
Each product's part in this workflow, with its current status.
- iFieldControlled beta
Gives representatives location-recorded check-in and a short outcome form in a phone browser, so each visit ends with a recorded result and a next action.
- CRMControlled rollout
Is designed to keep the visit outcome and the follow-up date on the customer's timeline, where the next person looks first. Recording them there is demonstrated in testing.
- iSalesControlled rollout
Holds the deals the visit relates to; the account owner updates the stage with the visit outcome in view.
What your business gains
- Managers see completed visits and due follow-ups without calling each representative
- Less repeated reporting: the outcome is recorded once, at the visit
- The next contact with the customer starts from what was agreed on site
Each visit becomes a recorded next action, so follow-up no longer depends on someone remembering a phone call.
A useful measure for a pilot
Share of completed visits with a recorded outcome and a dated next action on the customer's timeline.
What this requires
This workflow runs on the shared customer record. Before a pilot, these need to be in place:
- Your customer accounts in the customer record, each with an owner.
- Representatives using a phone with a web browser, allowing location at check-in.
- Visit outcome options and follow-up rules agreed with your managers.
- Check-in confirmed on your representatives' own phones during the pilot, as acceptance on real devices is still to be completed.
Evidence and scope
Recording a visit outcome and next action on the customer's timeline, and notifying the manager, are demonstrated in testing on code not yet released to customers. A visit opening or moving a deal is planned: the account owner updates the deal.
- Demonstrated in testingthe connection passes automated tests in test environments, on code not yet released to customers.
- Plannedit is not built yet. It is shown so you can see the intended workflow.
Each product shows its own status, and none is described as released for general use. Your demo confirms what applies to your deployment.
A suitable starting option
Field team
Compare what this starting option includes, what it requires and what can be added. Packaging is agreed per deployment.
Questions about this workflow
Does a visit outcome open or move a deal by itself?
No. Recording the outcome and next action on the customer's timeline, and notifying the manager, are demonstrated in testing on code not yet released to customers. A visit opening or moving a deal is a planned connection: the account owner updates the deal.
Do representatives need to install an app?
No. As designed, they use a web browser on their phone and allow location when they check in.
Walk through a field visit with us
Tell us how your representatives record and report visits today. We show how an outcome would reach the customer record and the manager in your setup.
Request a tailored demo of this workflow