Ad Reporting and Attribution

Add a Configurable 'Unsend' Grace Period for SMS, Email and WhatsApp
It would be extremely valuable to have an optional, configurable grace period before outbound SMS, email and WhatsApp messages are actually sent. For example, an agency could enable a 2 to 3 min delay after clicking send, during which the message would remain pending and the user would have the option to cancel it. This would help prevent avoidable issues caused by human error, such as sending a message to the wrong contact, noticing a typo immediately after sending, using incorrect information, or sending something that needs to be revised. For agencies managing communication on behalf of multiple clients, a mistaken message can create much bigger consequences than a simple typo. It can affect client trust, create compliance or reputation concerns, trigger unnecessary conversations, and require additional work to correct something that could have been prevented with a very short grace period. Ideally, this could be: Optional at the agency or sub-account level Configurable, for example 1, 2, 3, or 5 minutes Available for SMS, email, and WhatsApp Clearly show the message as Pending Include a visible Cancel Send or Unsend option during the grace period Automatically send once the selected grace period expires This would not need to recall a message after it has already been delivered. The goal is simply to create a short safety window before dispatch. For teams sending a high volume of client communications, this could prevent a significant number of avoidable mistakes and make messaging much safer.
1
Simple Input Forms for Documents & Contracts Templates
We’re a video production company and use HighLevel’s Documents & Contracts feature heavily for proposals, agreements, and contracts. One limitation we’ve run into is how much setup is required when a team member needs to generate a document from a template with unique information. Our current workaround is: We built an internal form for our team to fill out the information needed for the contract. Every input on that form has to be created as a custom field. Those custom fields then live on the contact or opportunity record, even though most of that information is only relevant to that specific document. An automation takes those values, populates the document template, and sends it to the client. It works, but it creates a lot of unnecessary custom fields and adds complexity to something that could be much simpler. I’d love to see HighLevel add a "Use Template" workflow directly inside Documents & Contracts. When someone clicks "Use Template," HighLevel could open a simple form-style interface containing all of the variable fields for that template. The team member fills them in, clicks continue, and HighLevel generates the document with those values populated. Ideally, these would be document-level variables rather than contact or opportunity custom fields, so temporary contract information doesn’t have to permanently live in the CRM. It could look something like: Select Template -> Fill in Template Fields -> Preview Document -> Send Even better, actions or automations could be attached to the template so that once the information is entered, the document follows a predefined workflow. For teams generating a high volume of proposals, contracts, agreements, or other customized documents, this would make Documents & Contracts significantly faster to use while keeping CRM custom fields much cleaner.
1
Load More