Set a Custom URL for Unassigned Calendars in Sparkforge

A custom calendar URL replaces the system-generated slug with something readable and on-brand. Unassigned Calendars route bookings to a pool of users instead of one specific person, and a clear slug helps prospects know what they're booking.

Why use a custom slug

• Brand consistency: readable URLs like /demo-call look professional in email signatures, ads, and embeds.
• Memorability: short slugs are easier to recall and type.
• Routing clarity: a descriptive slug sets expectations when bookings go to a pool.
• Naming control: reserve slugs early so multi-location and multi-team setups stay organized.

Calendar types and where slugs live

• Unassigned: bookings go to a pool. The calendar gets its own custom URL.
• Assigned (User): bookings go to one specific user. Custom URL options vary by calendar type.
• Group: a separate Group booking link surfaces multiple calendars together. The Group link is independent of each calendar's individual slug.

Where the slug shows up

• The standalone link you copy from calendar settings.
• Embedded booking widgets on your Sparkforge website or external sites.
• Buttons, emails, SMS, and any CTA that links to the calendar.
• Group pages, when used — your individual slug stays available too.

API Domain and how the link looks publicly

The visible link combines your API Domain (the domain Sparkforge uses for system-generated links) with the slug you set on the calendar. Configure branding before sharing links so you don't have to update them later.

• Set your API Domain so calendar links render under your branded domain.
• Your custom slug appends to the calendar path under that domain.
• If you change the API Domain later, re-test all calendar links and update shared CTAs.

Naming conventions that scale

• Lowercase, hyphenated, short. demo-call, consultation.
• No spaces, special characters, or long strings.
• Use prefixes for multi-location or product-line setups: nyc-demo, plus-plan-onboarding.
• Track reserved slugs in a doc so teams don't collide.
• Test in an incognito window after publishing.

Renaming a slug after it's live

Editing a slug typically creates a new public link, and previously shared links stop working. Audit every place the link lives — websites, funnels, automations, emails, SMS, ads — and update them before announcing the change.

Permissions

• Users need permission to view and edit Calendars in the sub-account.
• If you're using a branded API Domain, an admin needs to configure it before you share links.

Setting up the custom URL

1. Go to Settings → Calendars.
2. Click Create Calendar (or open an existing Unassigned Calendar to edit).
3. Choose Unassigned Booking as the calendar type.
4. In Team & Event Setup, find the Custom URL field.
5. Type your preferred slug. The system runs an availability check.
6. A check mark means it's available — save the calendar. A cross means another calendar already uses that slug. Pick a different one.

Verify and share

1. Open the copied link in incognito mode.
2. Confirm it loads under your branded API Domain (if configured).
3. Test a dummy booking to verify routing.
4. Update every placement — sites, emails, SMS, ads, chat.

Troubleshooting

• URL not available: pick a different slug or add a location/product prefix.
• Validation fails: remove spaces and special characters; stick to lowercase letters and hyphens.
• Link won't open under branded domain: confirm the API Domain is configured and propagated. Re-copy the link after configuration.
• User can't edit: verify they have Calendar permissions in the sub-account.