Skip to content

Ticket first-response timestamp reporting property (distinct from SLA breach alerting)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Service Hub Professional.

Ticket4 stepsUpdated for HubSpot seat pricing
OutcomeEvery ticket gets a stamped first-response timestamp property the moment it leaves its initial status, so reporting on response speed does not depend on the SLA feature being turned on.
Workflow mapreporting-alerts-016
Ticket status changes away from initial stage leads to first_response_logged_at has a value?. first_response_logged_at has a value? leads to yes: Exit, already stamped; no: Set first_response_logged_at = current date/time. yes no Ticket status changes away from initial stage first_response_logged_at has a value? Exit, already stamped Set first_response_logged_at = current date/time
Ticket status changes away from initial stage leads to first_response_logged_at has a value?. first_response_logged_at has a value? leads to yes: Exit, already stamped; no: Set first_response_logged_at = current date/time. yes no Ticket status changes away from initial stage first_response_logged_at has a value? Exit, already stamped Set first_response_ logged_at = current date/time

When to use it, when not to

Use it

  • Use it when you want a first-response timestamp for custom reports (funnel, average time to first touch) independent of Service Hub's built-in SLA tracking.
  • Use it on portals where the SLA feature is off, not licensed for every pipeline, or configured differently from what this reporting property needs.
Read more on when to use itShow less

Skip it

  • Do not use it as an SLA breach alert. It stamps a moment in time. It does not compare that moment to a target and does not warn before a deadline. Use the native SLA feature (Settings > Objects > Tickets > SLA) for breach alerting.
  • Do not use it if "first response" must mean an actual agent-sent email reply rather than a status or stage change. This fiche uses the ticket's first status movement as the proxy signal, not true reply detection. (check in your portal: whether the current portal exposes a native workflow trigger keyed specifically to a first agent reply, as opposed to a general status or stage change, for teams that need the stricter definition)
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library