Default Setup Guide home pagelogo
  • Support
  • Dashboard
  • Dashboard
Documentation
Changelog
  • Resources
  • Contact Us
  • Blog
  • About Us
    • What is Default?
    Workspace Onboarding
    • Quickstart Guide
    Forms
    • Forms
    • HubSpot Forms
    • HTML Forms
    • Forms SDK
    • Forms Observability
    • Default Pixel
    Routing
    • Queues
    • Territories and Segments
    Scheduling
    • Events
      • Events Configuration
      • Event FAQs
    Data Marketplace
    • De-anonymization
    Nodes
    • Notifications
    Dashboards
    • Meetings
    Integrations
    • Zoom
    • Salesforce
    • Amplemarket
    • Attio
    Events

    Event FAQs

    Common questions regarding events & Default.

    Default sends confirmations when a meeting is booked, along with the calendar invite.

    The very first confirmation is the meeting confirmation page.

    For individuals using Google calendar, you may experience cases where the Default invite did not make it on the lead’s calendar. This is due to Google’s Unknown Sender policy. The unknown sender policy states that there must be at least one form of recognized communication between the recepitent and the sender’s domain, before Google accepts the event onto the calendar. This impacts all scheduling and meeting booking software, not just Default.

    Example:

    This is to be expected. The option to “preview link” is a way to review and verify the look & feel (design) of the scheduler / scheduling experience.

    This does NOT work as an availability debugger. The debugger is on the roadmap however.

    Default adds “invisible” meeting buffers to your calendar under the following circumstances:

    • The user has a meeting buffer configured under Settings > Availability
    • The admin has set it at the event level

    Meeting buffers are not added as physical calendar holds / busy time.

    Was this page helpful?

    Events ConfigurationCompany De-anonymization
    Powered by Mintlify