AI variables for source_extension and source_primary_department?

[accentlogic]

Team 3CX - Amazing work in the improvements in Update 9! The new fuzzy match will allow us to use an AI Receptionist as a dedicated Call by Name assistant on large systems that have many users with a mix of similar nicknames and legal names. The agent is properly finding Matt/Matthew, Martin/Marty, etc. without issue. Love it!

@nikolascx Two variables we'd really like to have are the source_extension and the source_primary_department. With this information provided to the agent we can send callers back to the source Digital Receptionist, filter Call by Name results to the primary department, and more. If a match is not found, we can offer to expand the search to companywide.

 

[nikolascx]

Thank you for the great feedback! Really happy to hear Update 9 and the improved fuzzy matching are working well for your Call by Name use case.

The <span>source_extension</span> and <span>source_primary_department</span> variables make sense, especially for scenarios where the AI Receptionist needs to route callers back to the originating Digital Receptionist or narrow the search by department before expanding companywide.

I’ll pass this feedback to the team for review. No promises at this stage, as AI is moving very quickly and we’re currently focused on a number of higher-priority improvements.

One area we still need to address is fallback handling in case AI Labs are not available. That would also be a good time for us to review the available variables and see what else may be needed.

Keep the feedback coming, and God bless!