Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Article 19: Customer Issue Escalation SOP — How Sales Should Handle Prospect or Customer Problems

Purpose:  This article shows you how to handle customer, prospect, or partner issues when they come up during sales activity.

Your goal is to respond professionally, gather the right information, document the issue in HubSpot, submit support when needed, and avoid making promises or guesses that create confusion.

You should use this SOP when a customer, prospect, referral partner, or internal stakeholder reports a problem that affects:

  • Sales follow-up
  • Onboarding
  • Access
  • Payments
  • Forms
  • Portals
  • HubSpot records
  • Support expectations
  • Customer experience
  • Deal timing
  • ChainIT Pay credibility
1. Your Role When an Issue Comes Up

When a prospect or customer reports an issue, your role is to:

  1. Acknowledge the issue.
  2. Gather clear information.
  3. Document the issue in HubSpot.
  4. Submit support when needed.
  5. Keep the customer or prospect informed.
  6. Escalate internally if the issue affects revenue, risk, onboarding, or customer experience.

Your role is not to guess the technical cause.

Your role is not to promise a fix time unless it has been confirmed.

Your role is to make sure the issue is captured, routed, and followed through professionally.

2. First Response to the Customer or Prospect

When someone reports an issue, respond calmly and clearly.

Use language like:

“Thank you for flagging this. I’m going to document the issue and get it routed through our support process so the right team can review it.”

Or:

“I appreciate you letting me know. I’m going to gather a few details, submit this through support, and follow up once we have a clear update.”

This shows ownership without overpromising.

3. What You Should Not Say

Avoid saying:

  • “I know what caused this.”
  • “This always happens.”
  • “This is broken.”
  • “That should not be happening.”
  • “I can fix it.”
  • “I guarantee this will be resolved today.”
  • “You must have done something wrong.”
  • “I’ll just handle it outside the system.”
  • “Don’t worry about submitting anything.”

These statements can create risk, confusion, or unrealistic expectations.

Stay professional and factual.

4. Gather the Right Information

Before submitting support, gather as much detail as possible.

Ask:

  • What were you trying to do?
  • What happened instead?
  • When did this happen?
  • What link, form, portal, or system were you using?
  • Did you receive an error message?
  • Can you send a screenshot?
  • Is anyone else affected?
  • Is this blocking you from moving forward?
  • Is there a deadline or urgent business impact?

The better your information, the faster the support team can understand the issue.

5. Identify the Type of Issue

Try to classify the issue before you submit support.

Common issue types include:

  • HubSpot issue
  • Customer portal issue
  • Onboarding issue
  • Payment-related issue
  • Form or link issue
  • Login or access issue
  • Data issue
  • Email or communication issue
  • Support process issue
  • Sales process issue
  • Partner issue
  • Customer complaint
  • Deal blocker

You do not need to diagnose the root cause.
You only need to describe the issue clearly.

6. Determine Whether It Is Customer-Facing

Ask yourself:

  • Is the customer or prospect directly affected?
  • Is the issue blocking onboarding?
  • Is the issue delaying a Deal?
  • Is the issue affecting a live customer?
  • Is the issue visible outside ChainIT Pay?
  • Could this impact trust or credibility?
  • Could this affect revenue?

If yes, document it carefully and escalate if needed.

Customer-facing issues usually deserve more urgency than internal training questions.

7. Document the Issue in HubSpot

If the issue is connected to a Contact, Company, Lead, or Deal, document it in HubSpot.

This creates sales context.

You should add a note to the relevant record explaining:

  • Who reported the issue
  • What happened
  • When it happened
  • What system or process was affected
  • Whether support was submitted
  • Whether the issue affects timing, onboarding, or revenue
  • What the next step is

Do not rely only on the support ticket.

HubSpot should show the sales impact.

8. Contact Record Note Example

Use this when the issue is tied to a person.

Example:

“Customer reported an issue accessing the onboarding link on June 5. They received an error message after clicking the link. Support request submitted through support.chainit.com. Awaiting review. Follow-up task created.”

9. Company Record Note Example

Use this when the issue affects the business account.

Example:

“ABC Chiropractic reported a customer-facing onboarding access issue. This may delay their ability to move forward. Support ticket submitted. Monitoring impact on sales timeline.”

10. Deal Record Note Example

Use this when the issue affects an active revenue opportunity.

Example:

“Deal may be delayed due to onboarding access issue reported by prospect. Support ticket submitted. Next step is to follow up after support confirms resolution path.”

11. Submit the Issue Through ChainIT Support

Use the ChainIT Support Portal when the issue needs tracking:

https://support.chainit.com/

Your support request should include:

  • Your name
  • Customer or prospect name
  • Contact, Company, Lead, or Deal name
  • System affected
  • What the customer was trying to do
  • What happened instead
  • Error message
  • Screenshot
  • Business impact
  • Urgency level
  • Whether the issue affects an active Deal or onboarding

Support creates the trackable issue record.

HubSpot creates the sales context.

Use both when the issue affects a customer, prospect, or opportunity.

12. Choose the Right Urgency

Use urgency carefully.

Urgent

Use urgent when the issue is actively blocking revenue, onboarding, access, payment activity, or customer experience.

Examples:

  • Customer cannot complete onboarding.
  • Payment-related issue is active.
  • Customer-facing portal or link is down.
  • High-value Deal is blocked.
  • Multiple customers or users are affected.
  • Compliance or risk concern exists.
High Priority

Use high priority when the issue is important but not fully stopping business.

Examples:

  • Active prospect is experiencing a system issue.
  • Email plugin issue affects active Deal follow-up.
  • Deal record issue affects pipeline movement.
  • Customer has a problem that needs timely review.
Normal Priority

Use normal priority when the issue needs help but is not time-sensitive.

Examples:

  • Non-urgent record correction.
  • Help understanding a process.
  • Minor customer question that is not blocking progress.
Low Priority

Use low priority for suggestions, future improvements, or non-blocking questions.

13. When to Escalate Internally

Some issues need more than a support ticket.

Escalate internally when:

  • A customer is at risk.
  • A Deal is at risk.
  • A partner relationship is affected.
  • A high-value opportunity is blocked.
  • A customer-facing system appears down.
  • Multiple users or customers are affected.
  • A payment issue may create financial exposure.
  • A compliance, risk, or underwriting concern exists.
  • Leadership needs visibility.

Escalation does not replace the support ticket.

Submit the support ticket first, then escalate when business impact requires it.

14. How to Communicate After Submitting Support

After you submit support, follow up professionally.

You can say:

“I’ve submitted this through our support process and documented the issue. I’ll follow up once I have a confirmed update.”

Or:

“This has been routed for review. I’ll keep an eye on it and update you once the next step is confirmed.”

Do not say:

  • “It will be fixed today.”
  • “Support will call you immediately.”
  • “This is definitely a system issue.”
  • “I already know the cause.”

Only share confirmed information.

15. Create a Follow-Up Task

If the issue affects a customer, prospect, Lead, or Deal, create a follow-up task.

Examples:

  • Follow up with customer after support review.
  • Check support status tomorrow.
  • Confirm onboarding link works.
  • Update prospect after support response.
  • Review Deal timing after issue resolution.
  • Notify manager if issue remains unresolved.

Do not rely on memory.

Create the task in HubSpot.

16. How to Handle a Customer Who Is Frustrated

If the customer is frustrated, stay calm.

Use language like:

“I understand why that would be frustrating. I’m going to make sure this is documented clearly and routed to the right team so we can review it properly.”

Then focus on facts.

Ask:

  • What happened?
  • When did it happen?
  • What were you trying to do?
  • Do you have a screenshot?
  • Is this blocking your next step?

Do not become defensive.

Do not blame the customer.

17. How to Handle a Prospect Issue During an Active Deal

If the issue affects an active Deal:

  1. Document the issue on the Deal record.
  2. Submit support.
  3. Create a follow-up task.
  4. Update the close date if timing is affected.
  5. Add a note explaining the impact.
  6. Escalate if revenue or customer trust is at risk.

Your Deal should reflect reality.

If the issue delays the sale, the Deal record should show that.

18. How to Handle a Partner-Reported Issue

If a referral partner or business partner reports an issue:

  1. Thank them for flagging it.
  2. Gather details.
  3. Identify the customer or prospect affected.
  4. Document the issue in HubSpot.
  5. Submit support.
  6. Notify Sales Ops or leadership if the partner relationship is important.
  7. Follow up professionally.

Partner issues should be handled carefully because they can affect future referrals.

19. How to Handle Issues You Cannot Answer

If a customer asks a question you cannot answer, say:

“That is a good question. I want to confirm the right answer before I respond. I’ll review internally and follow up.”

Then:

  1. Log the question in HubSpot.
  2. Create a task.
  3. Ask Sales Ops, support, risk, compliance, product, or leadership as needed.
  4. Follow up once confirmed.

Do not guess.

20. What to Do If the Issue Is Actually a Data Problem

Sometimes a customer issue may actually be a HubSpot data problem.

Examples:

  • Wrong Contact associated with Company
  • Wrong owner
  • Duplicate Company
  • Missing Deal
  • Bad email address
  • Incorrect record history
  • Wrong campaign list

If so:

  1. Document the data issue.
  2. Avoid creating duplicates.
  3. Submit a data cleanup request.
  4. Add a note on the relevant record.
  5. Continue sales follow-up only after the correct record is identified.
21. What to Do If the Issue Is Resolved

When the issue is resolved:

  1. Update the customer or prospect if appropriate.
  2. Add a note in HubSpot.
  3. Complete the follow-up task.
  4. Update the Deal stage or close date if needed.
  5. Continue the sales process.
  6. Document any lesson learned if it may help the team.

Example note:

“Support confirmed onboarding link issue was resolved. Customer notified. Follow-up call scheduled for Friday to continue onboarding discussion.”

22. What to Do If the Issue Is Not Resolved

If the issue remains unresolved and affects sales or customer experience:

  1. Follow up through the support process.
  2. Update the HubSpot record.
  3. Notify your manager or Sales Ops.
  4. Escalate if the issue affects revenue, onboarding, or customer trust.
  5. Keep the customer informed without overpromising.

Do not let unresolved customer issues disappear.

23. Common Escalation Mistakes to Avoid

Avoid:

  • Guessing at the cause
  • Promising a fix time
  • Failing to submit support
  • Failing to document in HubSpot
  • Not creating a follow-up task
  • Not updating Deal timing
  • Telling the customer too much internal detail
  • Blaming another team
  • Handling issues only through text or side conversations
  • Forgetting to follow up after support responds
24. Customer Issue Checklist

When a customer or prospect reports an issue, confirm:

  • I acknowledged the issue professionally.
  • I gathered the facts.
  • I asked for screenshot or error message if available.
  • I identified the affected Contact, Company, Lead, or Deal.
  • I submitted support if tracking is needed.
  • I documented the issue in HubSpot.
  • I created a follow-up task.
  • I escalated if revenue, onboarding, risk, or customer trust is affected.
  • I avoided guessing or overpromising.
25. Final Standard

When a customer, prospect, or partner reports a problem, you should own the communication and route the issue properly.

The ChainIT Pay customer issue escalation standard is:

  • Acknowledge professionally.
  • Gather clear details.
  • Do not guess.
  • Do not overpromise.
  • Submit support when tracking is needed.
  • Document the issue in HubSpot.
  • Create follow-up tasks.
  • Escalate when revenue, onboarding, risk, or customer trust is affected.
  • Follow through until the issue has a clear next step.

Customer issues are not just support problems.

They affect trust, pipeline, and customer experience.

Handle them with discipline.