Default Integration
Overview
Aimdoc's Default integration lets visitors qualify and schedule meetings with the right rep using your existing Default forms and team routing. Aimdoc passes contact and qualification data into a Default form, which then routes the visitor to the appropriate calendar.
Features
- Form-Based Routing: Use a Default form to qualify and route visitors to the right team member.
- Team Distribution: Apply Default's routing logic and team rules to assign meetings.
- Inline Scheduling: Visitors can book directly inside the Aimdoc conversation once routed.
Before You Start
- A Default account with a configured form and team.
- The Form ID and Team ID for the form you want Aimdoc to use. See Default's Forms SDK documentation for where to find these.
- In Aimdoc, your agent collects the fields your Default form expects (for example, name, email, company size, etc.).
Setup Instructions
Step 1: Get Your Form ID and Team ID From Default
In your Default dashboard, open the form you want to use with Aimdoc and copy:
- Form ID — identifies the specific form to load.
- Team ID — identifies the team that owns the routing rules.
Step 2: Connect Default In Aimdoc
In the Aimdoc dashboard:
- Go to Integrations.
- Select Default.
- Enter the Form ID and Team ID copied from Default.
- Click Connect.
Step 3: Map fields in Actions
In Aimdoc:
- Go to your agent's Actions tab.
- Select Default under Scheduling.
- For each Aimdoc field your form uses, enter the corresponding Default form field key.
- If a mapped field is a dropdown or multi-select and Default expects different values than your option labels, fill in Option Values. Leave a row blank to send the option text as-is.
- Save the action.
Step 4: Use Default In Your Agent
Configure your agent's workflow so that scheduling fires through Default at the appropriate point in the conversation. Aimdoc passes the mapped contact and qualification data into the Default form so routing rules have what they need.
Workflow Requirement In Aimdoc
If your Default form expects a specific field, that field must be collected in the agent's workflow track path (current track or parent tracks). If a required field is missing, Aimdoc blocks publishing until the field is added.
Verify Your Setup
- Start a test conversation with your agent.
- Reach a workflow path that triggers scheduling.
- Confirm the Default form and routed calendar load in chat.
- Complete a test booking and verify it routes correctly inside Default.
Troubleshooting
- Form does not load: Double-check the Form ID and Team ID values in Aimdoc.
- Wrong routing result: Review your Default form's routing rules and confirm the mapped field values (including Option Values) match what the rules expect.
- Missing data in Default: Make sure each required field is collected by Aimdoc before scheduling fires.
Default Documentation
Need Help?
If you encounter any issues with your Default integration, please contact our support team at support@aimdoc.ai.