To customize your heyLibby white label, log into your white label website and to to the page ending in /partner-admin. You’ll also see the Partner Admin Portal in your upper right account menu.
For example, if your heyLibby website is https://help247.myassistant.ai, you would go to https://help247.myassistant.ai/partner-admin.
This section controls the highest-level branding and self-service options your customers will see in the white-labeled portal.
All changes take effect immediately after you click Save at the bottom of the page.
| Field | What it does | Editable by you? | Tips, Instructions, & Notes |
|---|---|---|---|
| Portal Domain | The URL where your customers log in (e.g., portal.acme.ai). |
No – contact us if you need it changed. | Pick a short, memorable sub-domain when you first onboard. Changing it later will break bookmarked links and email templates. |
| Partner Name | Friendly company name shown throughout the portal. | Yes | Use the name your customers already recognize (e.g., Acme Fitness). |
| Product Name | The label you give to the heyLibby product you resell. | Yes | Examples: Acme Connect, AI Assistant. Keep it short—this appears in menus and messages. |
| Show Embedded Chat | Toggles whether a live chat widget appears inside your customers’ portal. | Yes | ✅ On ➜ requires a valid Embedded Chat Agent ID (next field).🚫 Off ➜ the chat is hidden. |
| Embedded Chat Agent ID | This is the ID of the agent that you would like to use for the embedded chatbot in your white-label portal. Your customers will be able to see and interact with this embedded chatbot agent. | Yes | • Create an assistant first and edit all details for your chatbot.. |
• Copy everything after agent= in the URL (e.g., d69aec85-f2e0-4c8f-b44a-a96c821e13f8) and put that in this Embedded Chat Agent Id field. |
|||
| • Turn the Show Embedded Chat switch on. | |||
| Manage Plan Button Link | Adds a Manage Plan button on each customer’s Account page that redirects to an external billing or upgrade page. | Yes | Leave blank if you do not offer self-service plan management. |
| Partner Upgrade Message | Coming Soon | – | You can ignore this field for now. |
| Demo Link | Places a demo link on the onboarding page (yourdomain.com/onboarding) in the top right corner. | Yes | Perfect for routing new users to Calendly, HubSpot, etc. If blank, the link is hidden. |
| Default Assistant Name | The name that appears in chat, email, and voice introductions (e.g., “Hi, this is Libby, your AI assistant”). | Yes | Pick a gender-neutral name—customers may choose either a masculine or feminine voice.• Short, two-syllable names work best for TTS clarity. |
| Default Service | Pre-fills the “Service” input in onboarding. | Yes | Leave blank if your clients span many industries. If all customers share one vertical (e.g., Plumbing), enter it here for a smoother signup flow. |
| Default Assistant Email Domain | Determines the domain used when we auto-generate each assistant’s email (e.g., [email protected]). |
No | Recommended: keep the default help247.ai.Why? Most customers forward from their own address (e.g., [email protected]), so the system address stays hidden.Provisioning a custom domain requires that no other mail service is using it. You must delegate both inbound and outbound mail to us by pointing the domain’s MX records to our mail servers.Sub-domains (assistant.mail.acme.com) are discouraged—many ESPs flag them, DMARC alignment is trickier, and deliverability can drop. Contact support if you still want a custom domain and we’ll walk you through. |
| Notification Email | This is the email that new contact notifications are sent to customers from if they have email notifications turned on. | No | Managed on our side. This is the email that new contact notifications are sent to customers from if they have email notifications turned on. |
| Show Branding (for chatbot) | Allows your customers to toggle your logo in their chat widget. | Yes | Turn off to hide the option entirely; turn on so customers can enable/disable partner branding per assistant. |
| Show Character (for chatbot) | Lets customers display your logo/mascot in the chat widget. | Yes | We can upload a bespoke character for your brand. Disable if you prefer a minimalist look. |
| Billing Email (customer-visible) | Used throughout the portal to tell your customers who to reach out to for billing assistance. | Yes | The address customers should use for subscription or payment questions (e.g., [email protected]). |
| Support Email (customer-visible) | Used throughout the portal to tell your customers who to reach out to for general support. | Yes | Your main helpdesk address (e.g., [email protected]). |
| Tracking Email | This is the email that will receive credit card notifications for your account (if you pay by credit card.) | Yes | |
| Collection Email | This is the email that heyLibby will send the monthly invoice to (if you pay by invoice.) | Yes | |
| Legal Company Name | Appears wherever the portal references the entity providing service (e.g., “Terms of Service between Acme AI Corp. and Customer”). | Yes | Use the name exactly as it appears on your incorporation documents. |
| Legal Company Address | Used for documentation | Yes | Include street, suite, city, state/province, and ZIP/postal code. |
| State/Province and Country of Incorporation | Appears in Terms of Service | Yes | Format as State/Province, Country (e.g., Delaware, United States). |
| List of allowed query parameters | Lets you specify which URL parameters we should preserve during onboarding. Any parameter in this list is appended to the SSO callback URL after onboarding completes. | Yes (only for SSO partners) | Populate if you pass marketing tags such as utm_source, utm_campaign, or custom identifiers. Leave blank if you do not rely on query parameters or are not using SSO. |
On the branding page, you can also set the colors, links, and images for your site. Some of the sections on this page are not currently in use
If you have any questions, let us know.
<aside> 🚨
Only use 6 character hex codes, any other amount will NOT save
</aside>