90101: Unique Name Already Exists

This error occurs when you create or update a Conversation Intelligence (classic) Intelligence Service with a UniqueName that is already assigned to another Service. Twilio requires uniqueName when you create a Service, uses it as a unique and addressable name in addition to the Service sid, and lets you fetch a Service by its sid or unique_name.

• The UniqueName in your request already belongs to an existing Intelligence Service.
• You tried to update a Service and set uniqueName to a value that is already assigned to another Service.
• A previous create request already succeeded, and a retry submitted the same UniqueName again.

• Use a different UniqueName when you create or update the Service.
• Fetch the existing Service by sid or unique_name, or fetch multiple Services, to confirm which name is already in use before retrying the request.
• If you want to keep using the existing Service, update that Service instead of creating another one with the same UniqueName.
• If the existing Service is no longer needed, delete it and then retry the request.

• Conversation Intelligence (classic) Service Resource
• Conversation Intelligence (classic) onboarding guide
• Conversation Intelligence (classic) API overview