A new lead enters Hubhus and the first follow-up can be delayed by the next call, meeting or task on the sales team’s list. Hubhus’s New Lead trigger gives that lead an immediate path to Mobile Message, so a Zap can send a useful SMS while the enquiry is still fresh.

The workflow can text a salesperson with the lead’s details, or send the lead a short acknowledgement when a suitable mobile number is available. This removes the need to monitor the Hubhus pipeline for every new record. If a prospect replies to the SMS, Mobile Message’s Inbound SMS Received trigger can start a separate Zap using Hubhus’s Create Lead action. That creates a lead record from the incoming conversation, but it is a separate one-way automation rather than a synchronised update.

Zapier connects your Hubhus and Mobile Message accounts. Select the event or reply route, map the lead fields, write a plain-text message and test the number before enabling the Zap. Hubhus’s Update Lead and Delete Lead actions are available, though they are not needed for the most direct SMS workflows.