Puzzel

What Stevin gets out of Puzzel

Puzzel is not a marketing tool but a contact center platform, and that is immediately the interesting part: it sits on customer interactions that most marketing stacks never see, with its own reporting on top. We connect Puzzel data to marketing reports where the question is whether a campaign produces more calls or tickets, and whether that is good or bad news. Where it pinches is that Puzzel reports within its own walls: it shows what happens in the contact center, but it draws no line of its own to your campaigns or the rest of your data. That bridge is missing. Stevin runs on top and reads the interaction data together with your channel data, so a spike in calls after a campaign becomes a signal instead of a loose chart, with follow-up underneath and a person reviewing every action that carries weight first.

What you pair it with

Choosing Puzzel means you have a rich source of customer interactions that by default sits apart from your marketing. Count on a connection or an intermediate layer to get that data alongside your campaign insight, because Puzzel does not come to your reporting on its own. In practice: treat the contact center as a measurement source, not as an island. The question that remains is who draws the line between what a campaign does and what comes in afterward in calls, because on their own both tell you half the story.

Common mistakes

• →Leaving contact center data apart from marketing, so the connection stays invisible.
• →Assuming Puzzel draws the bridge to your campaigns on its own.
• →Not linking a spike in calls to the campaign that caused it.
• →Confusing Puzzel's own reporting with a complete picture.