Salesforce consulting and implementation services
FyerX helps sales and service teams make Salesforce useful from the first enquiry through account management and support. We configure Sales Cloud, Service Cloud and Experience Cloud around ownership, pipeline discipline and the information a customer is allowed to see.


When to bring in FyerX
One reason to review Salesforce opportunity management is a converted lead that matches two subsidiaries under one parent. It raises questions about contact email, account identifier, opportunity owner and original campaign, the groups affected and the action each can take when something goes wrong. Our starting point is the lead, account and opportunity history. We trace it from campaign response to accepted opportunity with the people who own those decisions. The result gives your Salesforce product owner a specific first release, a testable operating outcome and a record of dependencies. For this example, the practical standard is simple: revenue operations can count a conversion once and retain service history.
Forecasting and service handoff
Agree when an opportunity becomes forecastable and what service needs after signature. Preserve any entitlement start date, implementation contact and contracted service level in records the support team can use. Sales should be able to explain the handoff without exporting a spreadsheet.
Sales Cloud configuration
Set lead assignment, qualification criteria, opportunity stages and account relationships. Model an actual sales conversation before asking a representative to complete more required fields. Bring the lead, account and opportunity history and its history to the design discussion. Check contact email, account identifier, opportunity owner and original campaign against the policy in effect at the time. For a case involving a converted lead that matches two subsidiaries under one parent, ask how the team currently recognises that the decision is complete. Agree whether a customer contact can be linked to the correct legal entity.
Service Cloud implementation
Define case intake, queue rules, entitlements and escalations. Test a complaint that needs both a support agent and an internal engineering task before closure. Include sales representative, service agent and revenue operations manager in the walkthrough. Each sees a different part of the lead, account and opportunity history. Ask them to trace campaign response to accepted opportunity and establish where permission to see cases raised by a partner account actually sits. Differences between the documented responsibility and the person carrying out the action belong in the scope.
Experience Cloud portals
Configure external access around account relationships, supported tasks and content visibility. Verify a partner user cannot read another partner’s account or case notes. Work through an account transferred to a new territory midway through an open deal. Inspect the opportunity stage history and account ownership history before and after the event and ask the receiving team to explain the difference. A useful test includes partner reassignment and reopened opportunities, especially when the business consequence is an opportunity being created against the wrong subsidiary. Agree which information to keep and who will use it during a quarterly forecast review.
Illustrative engagement
Pipeline reports count the same deal twice
Starting point
An inbound demo creates a lead even though the account owner already has an open opportunity.
Decision
Review matching rules, lead conversion and account assignment using a small set of known duplicate records.
Deliverable
A repeatable conversion path that preserves campaign history and routes the deal to one owner.
Salesforce integrations and releases
Define where account, order and billing records originate. Rehearse bulk updates, integration failures and changes to roles in a representative sandbox before production rollout. For operational handover, give the Salesforce product owner a worked example from the quarterly pipeline movement report. Reconcile the result against qualified opportunities reconciled to their source leads. Agree how to queue ambiguous record matches for the account owner before consolidation when the evidence falls outside the accepted range.
Testing the opportunity lifecycle
Take one lead from a campaign through qualification, conversion, opportunity and closure. Include an existing contact and two opportunities on the same account so the test covers common ambiguities. Ask marketing which campaign should receive credit, ask sales which owner should get the follow-up task and ask service when entitlement begins. These are business decisions with downstream reporting consequences. Configure and test them against the same example so a local improvement to lead conversion does not create a duplicate customer or a support case with no entitlement. Keep the example with release evidence for subsequent automation changes.
Decide what happens when an account changes hands
An opportunity moving between territories can quietly break forecasts. The original owner still has an open activity, the new manager expects the opportunity in this month’s pipeline, and an integration continues to send updates to the old account team. We use a real territory change to test the proposed Salesforce model. Sales operations specifies who owns the opportunity and who needs continuing access. Finance defines which forecast category should change and when. Our configuration brief records those decisions alongside the stage criteria that sales managers will actually inspect.
Once the rules are clear, we rehearse the transfer in a sandbox with people from both territories. They inspect related contacts, open cases, activities, dashboard totals and any downstream CRM updates. A useful acceptance test is to have the receiving rep explain the next customer action directly from the transferred record. If they still need the previous owner's spreadsheet, we identify the missing field or process before deployment. The release notes also specify how to correct an accidental transfer without losing the history sales leaders depend on.
What to bring to discovery
Bring an anonymised lead, account and opportunity history, a recent quarterly pipeline movement report and an example of a converted lead that matches two subsidiaries under one parent. Where the inputs contain sensitive information, supply synthetic equivalents that preserve the decision sequence. Ask the Salesforce product owner to identify who may approve see cases raised by a partner account. Record contact email, account identifier, opportunity owner and original campaign with their meanings, including whether an empty value is permissible. Invite the people who use the opportunity stage history and account ownership history to describe the hardest discrepancy from the last cycle. The discovery log should capture the source evidence, responsible team and decision required.
Agreeing the first work package
Anchor the first work package in sales cloud configuration and choose a deliverable such as a role-based sharing matrix and conversion test pack. Define the boundary from campaign response to accepted opportunity so both teams know what a completed item looks like. For planning purposes, list partner reassignment and reopened opportunities separately from ordinary cases and record whether each is included in release one. Material scope changes include a new sales territory, a different owner for lead, account and opportunity history or a dependency that changes a quarterly forecast review. Agree the cost and acceptance consequence of each before committing delivery capacity.
An acceptance exercise for your team
Give the operators a qualified lead at a subsidiary of an existing strategic account. Ask the Salesforce product owner to describe the expected business result before showing them the implementation. Introduce a converted lead that matches two subsidiaries under one parent and follow the chain from campaign response to accepted opportunity. At each point, record the values of contact email, account identifier, opportunity owner and original campaign that matter to the decision. The test succeeds when revenue operations can count a conversion once and retain service history. If evidence from the opportunity stage history and account ownership history disagrees, stop at the first observable difference and establish who can resolve it. Keep the starting data and explanation with the quarterly pipeline movement report. This example can be adapted to the rules and responsibilities of your organisation.
What a service agent should see
Choose a closed-won opportunity with a support agreement and check the account from the agent's workspace. Identify which commercial terms the agent needs to honour and which details should stay with sales. Review field access and handover tasks together.
Planning around the operating calendar
Build the release around a quarterly forecast review. For Salesforce opportunity management, that means agreeing when the opportunity stage history and account ownership history are available, when the Salesforce product owner can decide and what work would be interrupted by a late change. Select test material covering partner reassignment and reopened opportunities before reserving a business sign-off slot. Treat permission to see cases raised by a partner account as a release dependency. If a new sales territory is introduced at the same time, check whether the original baseline for qualified conversions and stale opportunities by sales team still supports a meaningful comparison.
Exception ownership and recovery
One credible failure is an opportunity being created against the wrong subsidiary. The first diagnostic step is to inspect the opportunity stage history and account ownership history and identify the authoritative version of the lead, account and opportunity history. Next, determine whether a customer contact can be linked to the correct legal entity. For an incident involving partner users changing account affiliations, an operator may need to queue ambiguous record matches for the account owner before consolidation. Agree that authority with the Salesforce product owner ahead of a quarterly forecast review. Capture the resolution in a role-based sharing matrix and conversion test pack, including how sales representative, service agent and revenue operations manager can confirm recovery from their different perspectives. For repeat occurrences, compare the underlying fields rather than assuming every item in the exception queue has the same cause.
Handover and ongoing ownership
Put a role-based sharing matrix and conversion test pack in the hands of the staff who will own Salesforce opportunity management. Include a completed example from campaign response to accepted opportunity and a walkthrough for a converted lead that matches two subsidiaries under one parent. Someone outside the delivery team should be able to locate the opportunity stage history and account ownership history, identify permission to see cases raised by a partner account and act when the quarterly pipeline movement report shows a discrepancy. After the rehearsal, update ownership for lead, account and opportunity history and document where to propose changes to contact email, account identifier, opportunity owner and original campaign.
Planning your engagement
How to measure the outcome
Agree the measurement definition for qualified conversions and stale opportunities by sales team before changing Salesforce opportunity management. Start with qualified opportunities reconciled to their source leads, then review partner reassignment and reopened opportunities as a separate population if their expected treatment differs. A reliable baseline needs the reporting date, an owner for lead, account and opportunity history and a consistent definition of completion from campaign response to accepted opportunity. Test the quarterly pipeline movement report with a case involving a converted lead that matches two subsidiaries under one parent. If a new sales territory alters the population later, preserve the original baseline alongside the revised one. This gives the Salesforce product owner an explanation for a change in the number and a decision about which improvement to fund next.
Delivery and support responsibilities
For an advisory phase, ask FyerX to focus on the decision behind sales cloud configuration. For an implementation, agree the behaviour of lead, account and opportunity history through campaign response to accepted opportunity and the evidence required from the opportunity stage history and account ownership history. For a team that already owns delivery, a bounded specialist assignment can focus on experience cloud portals. Keep permission to see cases raised by a partner account with its named business or technology owner unless explicitly delegated.
Budgeting for a Salesforce release
Opportunity stages are quick to describe. Territory rules, account hierarchies, forecast rollups and inherited automation take longer to uncover. We review a sample of live deals, the current sharing model and the packages already installed. That gives the buyer a useful distinction between CRM configuration, data clean-up and integration work.
Frequently asked questions
Salesforce
How do lead conversion rules affect reporting?
Before enabling automation, agree what happens when an individual already exists as a contact but enquires about a different business unit. Test whether conversion creates a new opportunity, updates an account or routes the enquiry for review. The choice affects pipeline attribution and account ownership.
How should external sharing be tested?
Use sample users representing a partner administrator, partner representative and direct customer. Ask each to open the same case and related files. Check visibility after an account reassignment as well as at creation. A successful portal login proves very little about record-level access.
What would you need to assess Salesforce opportunity management?
Bring one lead, account and opportunity history, an example from the quarterly pipeline movement report and the people responsible for the opportunity stage history and account ownership history. A useful discovery exercise follows campaign response to accepted opportunity under both ordinary conditions and a converted lead that matches two subsidiaries under one parent. The resulting scope should identify the business decision, environment access and operating owner required for the first work package.
Can we begin with sales cloud configuration?
Yes. Define the first deliverable in terms of revenue operations can count a conversion once and retain service history. Agree with the Salesforce product owner how to test it using the opportunity stage history and account ownership history. The first phase can stop after the decision and evidence are delivered, or continue into service cloud implementation with scope and responsibilities already documented.
How does service cloud implementation fit into delivery?
It addresses the point in Salesforce opportunity management where the team must understand contact email, account identifier, opportunity owner and original campaign. Use a converted lead that matches two subsidiaries under one parent to establish how information, permissions and ownership cross that boundary. The resulting acceptance case should demonstrate a customer contact can be linked to the correct legal entity and identify who takes over if the outcome is uncertain.
What happens to cases involving duplicate accounts after conversion?
Use lead, account and opportunity history as the starting reference and examine the opportunity stage history and account ownership history. The key question is whether a customer contact can be linked to the correct legal entity. Agree a treatment with the Salesforce product owner, preserve evidence for the quarterly pipeline movement report and make the authorised next action visible to the team. Include the case in later release checks, especially after a new sales territory.
What happens when a partner user changes accounts?
Trace the user’s access to account records, contacts, cases and shared files before and after reassignment. Use a representative partner profile to test old links as well as the portal navigation. Keep any remaining access visible to the account and platform owners for review.
What should we expect at handover?
Expect the agreed delivery evidence and a role-based sharing matrix and conversion test pack. A useful sign-off is for the receiving team to trace campaign response to accepted opportunity, read the relevant entry in the quarterly pipeline movement report and respond to a converted lead that matches two subsidiaries under one parent using the material supplied. Document ongoing responsibility for updates to lead, account and opportunity history before closing the engagement.
How will our team decide whether to go ahead?
Ask whether revenue operations can count a conversion once and retain service history. Check the opportunity stage history and account ownership history with the Salesforce product owner and verify that permission to see cases raised by a partner account is available during a quarterly forecast review. If a critical dependency remains open, identify its effect on qualified opportunities reconciled to their source leads and the owner who can accept, resolve or defer it.
Which measures are useful after release?
Use qualified conversions and stale opportunities by sales team alongside the quarterly pipeline movement report. For Salesforce opportunity management, reconcile a sample against qualified opportunities reconciled to their source leads and review the influence of partner reassignment and reopened opportunities. Confirm that a new sales territory or a new reporting definition has not changed the population before crediting an improvement to the work.
Who can operate the outcome internally?
Agree responsibilities among the sales representative, service agent and revenue operations manager. Give the receiving operator an unfamiliar example involving partner users changing account affiliations and ask them to investigate it through the opportunity stage history and account ownership history. Their ability to explain campaign response to accepted opportunity and identify permission to see cases raised by a partner account is a practical test of the handover.
Who needs to be available during design?
Involve the sales operations owner who maintains forecasting, a seller who moves real deals through the pipeline and the administrator who maintains automation. Add a service lead if cases share customer records with sales.