Customerly API allows you to integrate your platform with Customerly's suite of customer support, marketing automation, and customer satisfaction software. This document provides an overview of how to authenticate and interact with the Customerly API.
\nTo interact with the Customerly REST API, you must authenticate your requests using an access token.
\nLog in to Customerly.
\nFollow the Tutorial: How to Obtain Your API Access Token in Customerly.
\nInclude the access token in the Authentication header of your HTTP requests.
In Customerly, it's essential to understand the distinction between Users and Leads, as they represent different types of contacts within the platform. They have specific properties and functionalities that cater to different aspects of customer management. For a complete guide on user properties, refer to the Contact Properties Documentation.
\nIn Customerly, we provide three distinct categories to help you recognize and communicate with different individuals interacting with your platform: Visitors, Leads, and Users. Understanding these categories is essential for effective engagement and customer management.
\nVisitors are individuals who visit your website without engaging with any features, such as the Live Chat widget. They are anonymous and typically lack identifiable information.
\nExample: Someone browsing your product pages without initiating a chat or signing up.
\nInteraction: None with your platform's interactive features.
\nData Collected: Minimal or none.
\nLeads are individuals who have shown some level of interest or engagement, such as starting a conversation through Live Chat. Any email collected through Live Chat is considered a Lead.
\nExample: Someone who asks a question about your products via Live Chat.
\nInteraction: Engaging with Live Chat or other interactive elements.
\nData Collected: Email and possibly other contact information.
\nIntegration: You can connect Customerly with your Facebook Ads to collect leads and initiate Funnels through tools like Zapier.
\nVisitors: Anonymous browsing without engagement.
\nLeads: Initial engagement through Live Chat or similar interactions.
\nUsers: Registered and fully engaged individuals with detailed profiles.
\nThese categories help you tailor your communication and marketing strategies, offering personalized experiences based on the individual's engagement level with your platform.
\nFor more details on how to work with Visitors, Leads, and Users in Customerly, refer to the related guides and documentation.
\nA contact property is a data point on your contact that allows you to store specific information related to that contact. These properties can be both default and customized, depending on your needs. Contact properties are essential for segmenting, filtering, and personalizing interactions with your contacts.
\nName: The identifier of the property, such as phone_number.
Description (optional): An internal description to help you recognize the property.
\nValue: The specific value you want to store for each contact for this property.
\nType: The type of value you will store, such as text, number, boolean, or date.
\nFor example, the phone_number property might have a name of \"Phone Number,\" a type of \"text,\" and store individual phone numbers as values for different contacts.
Contact properties can be powerful tools in managing and understanding your customer base. For a detailed guide on how to utilize contact properties within Customerly, including creating custom properties and managing default ones, refer to:
\n\nThis guide provides step-by-step instructions and best practices for working with contact properties in your Customerly account.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"Authentication","slug":"authentication"},{"content":"Basics","slug":"basics"}],"owner":"11487813","collectionId":"fb48c8d4-9898-4238-9a6d-6584dabd4d11","publishedId":"2s9Y5Wx3QG","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"2fb6fa"},"publishDate":"2023-08-24T15:44:34.000Z"},"item":[{"name":"User","item":[{"name":"Create or Update Users","id":"96e737e5-c3c4-4580-83d5-a935865a9486","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"users\":[\n {\n \"email\":\"luke@customerly.io\",\n \"user_id\": 40,\n \"name\": \"Luke\",\n \"attributes\": {\n \"phone_number\" : \"+353939200221\",\n \"revenues\" : 180000,\n \"website\" : \"https://www.customerly.io\",\n \"utm_medium\" : \"ppc\",\n \"utm_campaign\" : \"Remarketing\",\n \"utm_source\": \"meta\"\n },\n \"tags\":[\n \"onboarding\",\n \"remarketing\"\n ]\n }\n ]\n }","options":{"raw":{"language":"json"}}},"url":"https://api.customerly.io/v1/users","description":"The Users endpoint allows you to create, update, and manage users within Customerly, along with their subscription information, custom attributes, and tags. By integrating with this endpoint, you can unlock powerful capabilities to enhance user engagement, retention, and onboarding.
\nUpdate Subscription Information: Efficiently manage and update user subscription details, reflecting changes in plan, status, or preferences.
\nTrigger Workflows and Emails: Update properties or tags to fire specific workflows or personalized email communications. This enables targeted marketing and support interactions based on user attributes or behaviors.
\nWelcome Onboarding Workflow: Create a new user to automatically trigger a welcome onboarding email sequence. This fosters a positive first impression and guides the user through the initial stages of engagement with your platform.
\nName: The identifier of the property, such as subscription_plan.
Description (optional): An internal description to help you recognize the property.
\nValue: The specific value you want to store for each user for this property, such as plan type or subscription status.
\nType: The type of value you will store, such as text, number, boolean, or date.
\nFor example, the subscription_plan property might have a name of \"Subscription Plan,\" a type of \"text,\" and store individual subscription plans as values for different users.
Contact properties can be powerful tools in managing and understanding your customer base. For a detailed guide on how to utilize contact properties within Customerly, including creating custom properties and managing default ones, refer to:
\n\nThis guide provides step-by-step instructions and best practices for working with contact properties in your Customerly account.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"Fetch all the details of a single User searching by email.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"Fetch all the details of a single User searching by email.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"Fetch all the details of a single User searching by user_id.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"Your user Id
\n","type":"text/plain"},"key":"user_id","value":"40"}],"variable":[]}},"response":[{"id":"87fe1764-61ab-4447-a881-d099151090da","name":"GET User details by ID","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://api.customerly.io/v1/users?user_id=40","protocol":"https","host":["api","customerly","io"],"path":["v1","users"],"query":[{"key":"user_id","value":"40","description":"Your user Id "}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Date","value":"Thu, 24 Aug 2023 16:25:25 GMT"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"Set-Cookie","value":"AWSALB=arFWPKBPu77LL6TreE2N275z1xLU2vpM54O4cZwGPsAkRWRFGZtxs/9/pZ8UTyBB1TsJPefW1ijKXuyHoBMXC6NAIqWl+XS5+DCg51MPThrgjvjVqtCSRv+ypSIb; Expires=Thu, 31 Aug 2023 16:25:25 GMT; Path=/"},{"key":"Set-Cookie","value":"AWSALBCORS=arFWPKBPu77LL6TreE2N275z1xLU2vpM54O4cZwGPsAkRWRFGZtxs/9/pZ8UTyBB1TsJPefW1ijKXuyHoBMXC6NAIqWl+XS5+DCg51MPThrgjvjVqtCSRv+ypSIb; Expires=Thu, 31 Aug 2023 16:25:25 GMT; Path=/; SameSite=None; Secure"},{"key":"Server","value":"Apache/2.4.54 (Debian)"},{"key":"X-Powered-By","value":"PHP/7.4.33"},{"key":"Access-Control-Allow-Origin","value":"*"},{"key":"Access-Control-Allow-Methods","value":"GET, POST, PUT, DELETE"},{"key":"Access-Control-Allow-Headers","value":"content-type, authentication"},{"key":"Cache-Control","value":"no-cache, private"}],"cookie":[],"responseTime":null,"body":"{\n \"data\": {\n \"crmhero_user_id\": 29911301,\n \"app_id\": \"007b9e3f\",\n \"user_id\": \"40\",\n \"email\": \"elena@customerly.io\",\n \"name\": \"Elena\",\n \"is_user\": 1,\n \"last_page_viewed\": null,\n \"last_page_viewed_at\": null,\n \"ip_address\": null,\n \"timezone\": null,\n \"latitude\": null,\n \"longitude\": null,\n \"city\": null,\n \"postal_code\": null,\n \"region\": null,\n \"region_code\": null,\n \"country\": null,\n \"country_code\": null,\n \"continent\": null,\n \"continent_code\": null,\n \"isp\": null,\n \"browser_name\": null,\n \"browser_version\": null,\n \"browser_language\": null,\n \"spoken_language\": null,\n \"os\": null,\n \"os_version\": null,\n \"web_session\": null,\n \"first_seen_at\": 1692894190,\n \"android_app_name\": null,\n \"android_app_version\": null,\n \"android_device\": null,\n \"android_os_version\": null,\n \"android_session\": null,\n \"android_last_seen_at\": null,\n \"ios_app_name\": null,\n \"ios_app_version\": null,\n \"ios_device\": null,\n \"ios_os_version\": null,\n \"ios_session\": null,\n \"ios_last_seen_at\": null,\n \"picture_initials\": \"E\",\n \"picture_background\": \"af8b7c\",\n \"picture_gravatar\": 0,\n \"picture_gravatar_last_update\": 0,\n \"bounce\": 0,\n \"unsubscribe\": 1,\n \"spam\": 0,\n \"last_activity\": null,\n \"facebook_profile_id\": null,\n \"utm_campaign\": \"Remarketing\",\n \"utm_medium\": \"ppc\",\n \"utm_source\": \"meta\",\n \"utm_term\": null,\n \"utm_content\": null,\n \"referrer\": null,\n \"is_name_autogenerated\": 0,\n \"rating\": null,\n \"last_update\": \"2023-08-24 16:23:14\",\n \"was_lead\": 0,\n \"nps_vote\": null,\n \"attributes\": {\n \"phone_number\": \"+353939200221\",\n \"revenues\": \"180000\",\n \"website\": \"https://www.customerly.io\"\n },\n \"user_segments\": [],\n \"user_tags\": [\n \"onboarding\",\n \"remarketing\"\n ],\n \"user_events\": [],\n \"user_notes\": [],\n \"companies\": [\n {\n \"internal_company_id\": 1293944,\n \"app_id\": \"007b9e3f\",\n \"company_id\": \"a912c92\",\n \"name\": \"Company\",\n \"created_at\": 1664921391,\n \"last_seen_at\": 1681907658,\n \"attributes\": {\n \"address\": \"Ground Floor, 71 Lower Baggot Street\",\n \"admin_url\": \"https://www.company.com/admin/companyID\",\n \"city\": \"Dublin\",\n \"domain\": \"company.com\",\n \"employees\": \"10\",\n \"last_payment_amount\": \"1188\",\n \"phone\": \"21312312\",\n \"sub_amount\": \"1188\",\n \"sub_currency\": \"EUR\",\n \"sub_name\": \"Pro\",\n \"sub_period\": \"Yearly\",\n \"sub_state\": \"Active\",\n \"total_revenues\": \"5940\"\n }\n }\n ],\n \"n_open_conversations\": 0\n }\n}"}],"_postman_id":"c444946b-91e2-4538-8aae-5b521a614589"},{"name":"Delete User by Email","id":"3df1b211-fe5b-451e-8812-9a44eaf90cd7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"DELETE","header":[],"url":"https://api.customerly.io/v1/users?email=luke@customerly.io","description":"This endpoint allows you to permanently delete a contact from Customerly based on the email.
\n⚠️ This action is irreversible, so it should be used with caution.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"This endpoint allows you to permanently delete a contact from Customerly based on the unique user_id.
\n⚠️ This action is irreversible, so it should be used with caution.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"The Set User as Unsubscribed endpoint allows you to update a specific user's unsubscribe attribute to 1, thereby preventing further email communications from marketing campaigns.
\nHowever, this will not affect email communications related to support.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"Users are registered individuals on your platform, identifiable by user IDs, emails, and other data. They have specific profiles with detailed information.
\nExample: A registered customer with a user account on your platform.
\nInteraction: Full engagement with your platform, including purchases and account management.
\nData Collected: User ID, email, name, preferences, and other personalized data.
\nIntegration: To collect user session data and enable auto-login within Live Chat, you can follow this article.
\nFetch all the details of a single User searching by email.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"Fetch all the details of a single User searching by email.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"The Leads endpoint allows you to create or update leads within Customerly, along with any custom attributes and tags. This integration is particularly beneficial for lead generation campaigns, enabling you to pass leads to Customerly seamlessly and trigger personalized email sequences and workflows.
\nLead Integration: Easily pass leads from your platform to Customerly, ensuring that all relevant data is captured and managed efficiently.
\nEmail Sequences: Fire automated email sequences tailored to the lead's attributes, enhancing engagement and conversion.
\nWorkflow Automation: Trigger specific workflows based on lead attributes, facilitating targeted marketing and sales efforts.
\nDynamic Property Management: Whenever a new property (or attribute) is passed to this endpoint, it will be registered as a new property in Customerly, allowing for dynamic data handling.
\nName: The identifier of the property, such as phone_number.
Description (optional): An internal description to help you recognize the property.
\nValue: The specific value you want to store for each lead for this property.
\nType: The type of value you will store, such as text, number, boolean, or date.
\nFor example, the phone_number property might have a name of \"Phone Number,\" a type of \"text,\" and store individual phone numbers as values for different leads.
Contact properties can be powerful tools in managing and understanding your customer base. For a detailed guide on how to utilize contact properties within Customerly, including creating custom properties and managing default ones, refer to:
\n\nThis guide provides step-by-step instructions and best practices for working with contact properties in your Customerly account.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"This endpoint allows you to permanently delete a contact from Customerly based on the email.
\n⚠️ This action is irreversible, so it should be used with caution.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"Leads are individuals who initiate a conversation through Live Chat on your platform or submit a form on your landing page. Unlike registered users, leads may not have comprehensive profiles but are identifiable by their interactions and contact details, such as email addresses.
\nExample: Someone who starts a conversation on your website via the Live Chat widget.
\nInteraction: Engagement through Live Chat, often an entry point into your sales or support funnel.
\nData Collected: Email, name (if provided), and the conversation history.
\nIntegration Opportunities with Customerly's Leads REST API:
\nCollect Leads Through Live Chat: Every email collected through the live chat can be seamlessly integrated as a Lead within Customerly.
\nFacebook Ads Connection: You can connect your Facebook Ads to Customerly, enabling lead collection directly from advertising campaigns.
\nAutomate Funnels: Utilize Zapier to create automated funnels that guide leads through specific pathways, enhancing lead nurturing and conversion.
\nTrigger Email Sequences: Implement personalized email sequences for leads based on their attributes or interactions.
\nBenefits of Using the Leads REST API:
\nUnified Lead Management: Consolidate leads from different sources, including Live Chat and Facebook Ads, into a single platform.
\nAutomated Engagement: Create tailored email sequences and workflows to engage leads at the right time with the right message.
\nEnhanced Conversion: By understanding and interacting with leads effectively, you can increase conversion rates and move leads further down the sales funnel.
\nTags play a crucial role in categorizing, filtering, and targeting specific segments within your contact base. They enable a more personalized and efficient approach to email marketing automation, allowing you to align your communication with specific attributes or behaviors.
\nTags are labels or identifiers used to categorize something or someone within Customerly. Unlike properties, which consist of a name and value, tags are simple descriptors.
\nYou can assign tags to your contacts in several ways:
\nManually: Add tags directly in the contact details within Customerly Inboxes or CRM.
\nWorkflows: Utilize workflows to automatically tag contacts based on specific interactions or behaviors.
\nZapier: Integrate with Zapier to tag contacts from external sources or triggers.
\nAPI: Use Customerly's API to programmatically assign tags based on custom logic or integration with other platforms.
\nWhile tags are simple labels, properties consist of a property name and a value, functioning as added attributes for contacts.
\nTags: Used for categorization, such as \"happycustomers.\"
\nProperties: Include detailed attributes that can be updated, such as \"birthday,\" \"name,\" or \"country.\"
\nSegmentation: Easily segment contacts based on specific tags, enabling targeted marketing campaigns.
\nPersonalization: Utilize tags to personalize communication and enhance engagement.
\nAutomation: Incorporate tags within automated workflows to trigger specific actions or sequences.
\nThis request enables the creation of a new conversation within Customerly from a user to an admin (or teammate). It's particularly useful for automating support requests, allowing users to initiate conversations that land directly in the support inbox.
\nThis request facilitates automated support interactions, allowing users to send direct inquiries, product interests, or assistance requests to admins or support teammates. It ensures that support queries are routed efficiently and handled promptly.
\nUser Engagement: Provides users with a seamless channel to inquire or seek support, enhancing user satisfaction.
\nSupport Efficiency: Automates the support request process, routing conversations directly to the responsible admin or teammate.
\nFlexibility: Allows for the inclusion of attachments and personalized content, catering to diverse support needs.
\nRapid Response: Ensures immediate notification of errors or payment failures, allowing for swift resolution
\nUser Assurance: Provides users with a direct channel to seek help, enhancing trust and satisfaction.
\nWhat is Channel?
\nThe channel by defaul is messenger, but if you want to force it to email, you can do it so by adding channel email.
\nIn Customerly, an \"admin\" refers to a specific account that represents a teammate. Admins are typically responsible for managing various aspects of the platform, including customer support, handling inquiries, resolving issues, and more.
\nThe admin's ID is a unique identifier used to represent a specific teammate within Customerly. You can find the ID of an admin by following these steps:
\nLog in to Customerly: Ensure you are logged in to your Customerly account.
\nNavigate to Teammates Page: Go to the Teammates page by clicking on the following link: Teammates Page.
\nLocate the Teammates Table: On the Teammates page, you will find a table listing all your teammates.
\nFind the Admin's ID: Look for the specific admin whose ID you need, and you will find the ID listed under the Teammates table.
\nEnsure that the base64 field contains properly base64-encoded data for the attachment.
The type fields for both sender and recipient should match the respective roles within your system (e.g., \"user\" for end-users, \"admin\" for administrators or support teammates).
This request allows you to create a new conversation within Customerly from an admin to a user. It includes the message content, sender and recipient details, and optional attachments.
\nThis request is particularly useful when you want to create automated notifications or support interactions from an admin to a user. For example, notifying a user that their account has been activated or sending personalized communication with relevant attachments.
\nWhat is Channel?
\nThe channel by defaul is messenger, but if you want to force it to email, you can do it so by adding channel email.
\nIn Customerly, an \"admin\" refers to a specific account that represents a teammate. Admins are typically responsible for managing various aspects of the platform, including customer support, handling inquiries, resolving issues, and more.
\nThe admin's ID is a unique identifier used to represent a specific teammate within Customerly. You can find the ID of an admin by following these steps:
\nLog in to Customerly: Ensure you are logged in to your Customerly account.
\nNavigate to Teammates Page: Go to the Teammates page by clicking on the following link: Teammates Page.
\nLocate the Teammates Table: On the Teammates page, you will find a table listing all your teammates.
\nFind the Admin's ID: Look for the specific admin whose ID you need, and you will find the ID listed under the Teammates table.
\nEnsure that the base64 field contains properly base64-encoded data for the attachment.
The type fields for both sender and recipient should match the respective roles within your system (e.g., \"admin\" for administrators, \"user\" for end-users).
The /message endpoint in Customerly allows you to create a new conversation with a message, either from an account_id to a user_id or vice versa. This endpoint provides a robust solution for automating communication and support interactions within your platform.
Create Conversations: Initiate new conversations between accounts and users, seamlessly bridging communication within your platform.
\nAutomate Support Requests: Generate support requests from users programmatically, directly from your backend, facilitating quick responses and issue resolution.
\nFlexible Targeting: Send messages to specific user IDs or account IDs, ensuring that the communication reaches the intended recipient.
\nAutomated Support Tickets: Automatically create support tickets from users, triggering specific workflows or alerting support staff.
\nPersonalized Communication: Send targeted messages to users or accounts based on specific events, behaviors, or attributes.
\nIntegration with Other Systems: Leverage the /message endpoint to integrate with other systems, such as CRM or helpdesk solutions, creating a unified communication experience.
This is a test body article, I don't know what to write, sincerely.
I'm doing this for test, this is not bold.
\",\n \"status\": 0,\n \"num_visits\": 0,\n \"num_negative_reactions\": 0,\n \"num_neutral_reactions\": 0,\n \"num_positive_reactions\": 0,\n \"written_by\": 2,\n \"created_at\": 1681388417,\n \"updated_at\": 1681388417,\n \"sort\": 0,\n \"body_plain_lower\": \"this is a test body article, i don't know what to write, sincerely.i'm doing this for test, this is not bold.\",\n \"title_lower\": \"article title in english\",\n \"description_lower\": \"test description\",\n \"ai_enabled\": 1,\n \"ai_relevant_fields_last_update_at\": 0,\n \"ai_last_train_at\": -1,\n \"keywords\": [\n \"dontknow\",\n \"keyword\"\n ]\n }\n ]\n }\n}"}],"_postman_id":"3591bed7-d32a-404a-8df4-89b5baa57b50"},{"name":"Create Collection","id":"c98e1727-f2af-4683-9ba6-289c814c3505","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"title\": \"Required title\",\n \"icon\": \"Required icon\",\n \"slug\": \"Required slug\",\n \"description\": \"Optional description\",\n \"locale\": \"Locale in format iso 639-1\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.customerly.io/v1/knowledge/collections","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"This is a test body article, I don't know what to write, sincerely.
I'm doing this for test, this is not bold.
\",\n \"status\": 0,\n \"num_visits\": 0,\n \"num_negative_reactions\": 0,\n \"num_neutral_reactions\": 0,\n \"num_positive_reactions\": 0,\n \"written_by\": 2,\n \"created_at\": 1681388417,\n \"updated_at\": 1681388417,\n \"sort\": 0,\n \"body_plain_lower\": \"this is a test body article, i don't know what to write, sincerely.i'm doing this for test, this is not bold.\",\n \"title_lower\": \"article title in english\",\n \"description_lower\": \"test description\",\n \"ai_enabled\": 1,\n \"ai_relevant_fields_last_update_at\": 0,\n \"ai_last_train_at\": -1,\n \"keywords\": [\n \"dontknow\",\n \"keyword\"\n ]\n }\n ]\n}"}],"_postman_id":"23b2c63d-7116-4606-a7f0-0b281dcf8dfe"}],"id":"0abe45e5-5592-4956-873c-5b37fb1fc12c","_postman_id":"0abe45e5-5592-4956-873c-5b37fb1fc12c","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"The Knowledgebase API in Customerly empowers you to manage your help center content programmatically. It allows seamless integration of existing knowledgebase collections and articles, enabling you to add, edit, and import content directly into Customerly.
\nAdd Collections and Articles: Create new collections and articles, organizing content according to your needs.
\nEdit Existing Content: Modify existing collections and articles, updating information, and maintaining relevance.
\nImport Existing Help Center: Migrate content from any existing help center into Customerly with ease.
\nIntegration with Conversational AI: Leverage Customerly's Conversational AI capabilities to enhance user interactions and support.
\nAutomated Content Management: Handle collections and articles programmatically, saving time and resources.
\nEnhanced User Experience: Benefit from Customerly's Conversational AI, providing dynamic and personalized support to users.
\nContent Flexibility: Customize and organize your help center content to match your brand and user needs.
\nEasy Migration: Import existing help center content into Customerly, leveraging advanced features without losing valuable information.
\nImporting Legacy Help Center: If you have an existing help center, use the Knowledgebase Collection API to import all collections and articles into Customerly.
\nAutomated Content Updates: Keep your help center up-to-date by automating content additions and edits.
\nAI-Enhanced Support: Utilize Customerly's Conversational AI to provide intelligent and context-aware support, improving user engagement and satisfaction.
\nCreate a New Collection: Define categories and sections to organize articles.
\nAdd an Article: Insert detailed articles, guides, and FAQs to assist users.
\nEdit an Article: Update existing articles with new information or corrections.
\nImport an Existing Help Center: Migrate all content from another platform to Customerly, maintaining structure and content integrity.
\n