Introducing Lead Inquiry Auto-Responders

Introducing Lead Inquiry Auto-Responders
August 27, 2017

Aisle Planner Lead Inquiry Auto Responder

We almost can't believe that our Lead Management feature hit the scene more than a year ago. And today, we are thrilled to adding yet another upgrade to this key feature - auto-responders!
 
Your client experience starts before you actually have a chance to talk with your potential new clients so, making a strong first impression is important. And, our new auto-responder feature gives you the ability to kick off your client experience just moments after someone reaches out!  With a customizable message, name tokens, and the ability to attach your brochure, your leads will get to know (and love) you right away!

 

How to Set Up Your Lead Inquiry Auto Responder

To set up your auto responder simply click Settings from your Pro Dashboard and then Leads. You'll be dropped onto the page where you can customize your Lead Contact Form and you’ll see a new section titled “Auto Response” below the “Custom Welcome Message" section.

Once you are there, all you need to do is edit the subject, message and attach your brochure! The message includes tokens for the recipient’s name and your organization name and you can attach any document template as long as it does not require a signature.

Aisle Planner Lead Inquiry Auto Responder

To enable the auto-responder, click the button next to “Auto Response Currently Enabled." Simply uncheck that same box to disable it.

Things to Note About Lead Inquiry Auto Responders

  • The token in the auto-responder message will pull the recipient’s name {{fname}} from the Lead Contact Form and your organization name {{org_name}} from your Business Settings
  • When a lead replies to the automated message, replies will go to anyone in the organization that was assigned notification for leads. To manage those notifications, click the Manage Notifications button under the “Lead Notification” section of the Lead Form page
  • We recommend creating a brochure or some sort of document that provides more information about your services as a template to attach to your auto responder. Remember, it cannot have signature requirements
As always, if you have any questions about our new features, don’t hesitate to get in touch! You can check out our FAQs in our help center here or reach us at customercare@aisleplanner.com
Share

About the Author

Aisle Planner Editorial Team
Aisle Planner Editorial Team
The Aisle Planner Editorial Team is a collective of creative writers, editors, and former event pros who obsess over weddings and special events—and the businesses behind them! Drawn to refined details, design, and creativity, our team provides intelligent and straightforward articles with insights, practical tips, and expert guidance in putting Aisle Planner's "Power of One" behind your business.
The website encountered an unexpected error. Try again later.
TypeError: Drupal\ap_gallery\Plugin\QueueWorker\GalleryJsonQueueProcessor::__construct(): Argument #6 ($file) must be of type Drupal\s3fs\S3fsFileService, Drupal\s3fs\S3fsFileSystemD103 given, called in /var/www/ap/web/modules/custom/ap_gallery/src/Plugin/QueueWorker/GalleryJsonQueueProcessor.php on line 63 in Drupal\ap_gallery\Plugin\QueueWorker\GalleryJsonQueueProcessor->__construct() (line 46 of modules/custom/ap_gallery/src/Plugin/QueueWorker/GalleryJsonQueueProcessor.php).
Drupal\ap_gallery\Plugin\QueueWorker\GalleryJsonQueueProcessor->__construct() (Line: 63)
Drupal\ap_gallery\Plugin\QueueWorker\GalleryJsonQueueProcessor::create() (Line: 21)
Drupal\Core\Plugin\Factory\ContainerFactory->createInstance() (Line: 83)
Drupal\Component\Plugin\PluginManagerBase->createInstance() (Line: 63)
Drupal\Core\Queue\QueueWorkerManager->createInstance() (Line: 208)
Drupal\Core\Cron->processQueues() (Line: 162)
Drupal\Core\Cron->run() (Line: 75)
Drupal\Core\ProxyClass\Cron->run() (Line: 65)
Drupal\automated_cron\EventSubscriber\AutomatedCron->onTerminate()
call_user_func() (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch() (Line: 115)
Symfony\Component\HttpKernel\HttpKernel->terminate() (Line: 66)
Drupal\Core\StackMiddleware\StackedHttpKernel->terminate() (Line: 715)
Drupal\Core\DrupalKernel->terminate() (Line: 22)