Most of the work is building the component itself. Wiring it into the console takes a few clicks in Setup or App Builder.
- Build the component
Lightning Web Component, Aura, Visualforce, or Canvas. Pick based on existing codebase, modern best practice (LWC for new builds), or what the embedded content requires (Canvas for external apps).
- Add the component to the console app
In Setup, App Manager, edit the Lightning Console App. In App Builder, drag the component into the desired region (sidebar, footer, highlights). Save and activate.
- Configure permissions
Grant access to the component through permission sets. Components that read external data also need the supporting integration permissions.
- Test in the console
Open the console as an agent user. Confirm the component renders in the right region, shows the right data, and responds correctly to record navigation.
- Configure component-level settings
Many Custom Console Components have their own settings (data source, refresh interval, display options). Configure these per app or per user.
- Iterate based on agent feedback
Custom Console Components evolve based on real-world use. Build a feedback loop with the agent team to refine functionality.
- Visualforce Custom Console Components in Lightning console apps run through a compatibility iframe. The iframe adds overhead; LWC is faster.
- Component placement in App Builder is per console app. Adding to the Service Console does not add to the Sales Console; configure both if needed.
- External-data components have to handle authentication. Named Credentials are the recommended pattern, not stored API keys.
- Footer components are easy to overlook; agents do not see them unless they click. Test usability with real agents.
- Custom Console Components compete for screen real estate with the standard record view. Crowded layouts slow agents down; pilot carefully.