Portal and Multi-Channel Inbox Configuration
What this domain covers
Portal and Multi-Channel Inbox Configuration tests the customer-facing entry points: the support portal, custom domains, branding, languages, and the channel settings for email, chat, phone, social, messaging, and API sources.
Core rules and concepts
- The portal is available on the account subdomain and can use a custom domain via CNAME with SSL. DNS verification must complete before the branded domain works reliably.
- Portal settings control theme, logo, colors, languages, ticket submission fields, signup requirements, and knowledge-base visibility. Portal language and agent interface language are separate settings.
- Multiple portals or products may be available on higher plans, letting different brands or product lines have separate knowledge bases and submission forms.
- Channels include email, chat, phone, Twitter, Facebook, WhatsApp, Instagram, mobile SDK, API, and web widgets. Each channel has its own authentication or token that expires independently.
- A unified agent inbox presents channel conversations in the ticket view, but routing still depends on Dispatch’r, group settings, and channel configuration.
- Chat and messaging availability should align with business hours; otherwise customers see an offline experience while agents are working elsewhere.
Worked example
A company has two products with different brands. The admin creates two portals, each with its own custom domain and knowledge base, and routes each portal’s new tickets to a product-specific group. Social messages for both brands land in the same Freshdesk account but are routed by channel account and keyword rules. The reasoning: the portal controls self-service and form submission, while channel accounts and Dispatch’r control where conversations land.
Traps that cost marks
- Launching a custom domain before DNS and SSL verification complete.
- Confusing portal language with agent interface language.
- Letting social or messaging tokens expire, which silently stops new tickets.
- Assuming a unified inbox automatically routes to the right group.
- Leaving chat online outside business hours and creating unmet expectations.