Insert signatures in mobile sequences

Status: Idea Submitted

TL;DR:
HubSpot’s mobile app doesn’t include user signatures in sequence emails, unlike desktop. Adding automatic signature insertion on mobile is a basic feature that would ensure consistent branding, save time, and align mobile with desktop functionality.

Issue:

When sending emails through HubSpot Sequences on the mobile app, user signatures are not automatically appended. The same sequences correctly include the default signature when sent from the desktop version, but on mobile, outgoing sequence emails omit it entirely.

This inconsistency creates a professionalism gap for sales teams who work on the go and rely on the mobile app to maintain communication with prospects and customers. Manual insertion of signatures or editing each sequence template is inefficient and increases the chance of sending unbranded or incomplete emails.

Proposed improvement:
Enable the mobile app to automatically append the user’s default HubSpot email signature to all sequence messages, just as it does on desktop. Ideally, this should use the existing signature personalization token so the correct signature is pulled dynamically per email address.

Impact:

  • Ensures consistent branding and professionalism across all devices
  • Saves time for mobile users by removing the need to edit every template
  • Brings mobile feature parity with desktop sequences

I enroll new contacts in a sequence immediately (email templates) from the road on my phone everyday as I’m often in the field and cannot access my desktop. Not having an email signature looks werid and this would be a HUGE improvement for me.

I’m sure this feature used to exist as I’ve always used sequences on mobile but only noticed missing email signatures last year (around September maybe 2025) and this year (early 2026).

I’ve spoken with support and they advised it isn’t compatible, but I’m sure it was working and has recently thrown issues. Anyone else have the same experience? Or is this just me?

Either way, this definitely needs to be fixed/added