Support Automation #3373: NPS Collection with Intercom + HubSpot + WordPress

Problem

Agents switch between Intercom and HubSpot to complete nps collection, which slows resolution and fragments ticket history.

Connecting the tools keeps customer context in one thread.

Workflow

Intercom ticket event → classify/priority rules → update HubSpot → ping channel in WordPress.

Tools Used

• Intercom
• HubSpot
• WordPress

Setup Steps

1. Create credentials for Intercom, HubSpot, WordPress in your orchestration platform.
2. Define the nps collection trigger in Intercom.
3. Map required fields from Intercom to HubSpot.
4. Add error handling appropriate for a Medium workflow.
5. Run a test payload, then enable production execution (~23 min typical setup in our dataset).

Expected Outcome

• A repeatable nps collection path for support teams.
• Less context switching between Intercom and HubSpot.
• Easier hand-offs for the next ops owner.

Benefits & ROI

• Library metadata: Low ROI tier · Medium difficulty · ~23 min setup estimate.
• Reduces manual nps collection steps between Intercom, HubSpot, WordPress.
• Provides a baseline you can extend with approvals, logging, or QA gates.

Variations

• Batch non-urgent nps collection runs on a schedule instead of realtime.
• Archive raw payloads to a datastore for audit.

Troubleshooting

• Test reopened tickets to avoid duplicate threads.
• Map priority and assignee fields explicitly.
• Rate-limit high-volume webhook bursts from the helpdesk.