Touchpoint

Origin & evolution

The touchpoint comes out of service marketing and service design, where the central problem was that a service is produced and consumed in the same moments of contact. The concept gained breadth as journey mapping spread from the late 1990s onward, and it absorbed a useful taxonomy from media and marketing: touchpoints split by who controls them. Owned touchpoints are the ones a brand runs directly, such as its store, app, and support line. Paid touchpoints are bought, such as advertising and sponsored placements. Earned touchpoints are the ones a brand cannot purchase, such as reviews, press, and word of mouth, which carry more credibility precisely because the brand did not author them.

The 2009 McKinsey consumer decision journey sharpened why this matters. By modelling buying as a loop of consider, evaluate, buy, and post-purchase, it showed that the touchpoints doing the most work are often earned ones during active evaluation, when a prospect is reading reviews and asking peers, well outside the brand's direct control. The practical consequence: a brand cannot manage its experience by polishing only the touchpoints it owns, because the decisive contact may be one it can influence but never command.

How it works in practice

A direct-to-consumer mattress company audits its post-purchase experience. The journey map says delivery is a single happy stage. The touchpoint inventory tells a finer story. Order confirmation, an owned email, lands instantly and reads well. The shipping-carrier tracking page, an unowned touchpoint operated by a third party, is where customers spend the anxious week, and it shows a vague "in transit" with no delivery date.

That one touchpoint generates a measurable spike in support contacts, each an unplanned and expensive touchpoint of its own. The company cannot rebuild the carrier's page, so it inserts an owned touchpoint it controls: a branded tracking email with a firm delivery window, sent the moment the carrier scans the parcel. Support contacts in that window drop sharply. The experience improved at the level of a single contact, which is the only level at which experience is ever real.

Touchpoint vs. its neighbours

• Journey step🪜Journey StepExperience DesignA single step in a user journeyView reference → is what the customer is doing and intending at a moment; the touchpoint is the surface they do it on. A step such as "check delivery date" can occur across several touchpoints, and one touchpoint such as a tracking page can host steps from several journeys. The graph ties them with touchpoint_occurs_in_journey_stepTouchpointoccurs inJourney Stepcross-domain.
• Customer journey stage🚏Customer Journey StageCustomer SuccessA stage in the post-sale customer journeyView reference → is a phase of the relationship, such as evaluation or retention. A stage contains many touchpoints. The touchpoint is one contact inside the stage, and it is where the stage either delivers on its promise or fails.
• Channel is the medium a touchpoint runs through, such as email, web, phone, or retail. One channel carries many touchpoints; the touchpoint is the specific contact, the channel the pipe it travels.

In the graph

In the Unified Product Graph, a touchpoint sits in the customer-success domain as the unit of contact between customer and product. It nests under the phase it belongs to through customer_journey_stage_contains_touchpointCustomer Journey StagecontainsTouchpointhierarchy, and it connects to the customer's intent through touchpoint_occurs_in_journey_stepTouchpointoccurs inJourney Stepcross-domain. That pairing is the point of the structure. The journey step holds what the customer wants; the touchpoint holds where that want is served or dropped. Modelling both, and the link between them, means a failing experience can be traced to a specific contact and the specific moment of intent it betrayed, down past the stage that looked fine in aggregate.