This guide provides an overview of the key terms and concepts you’ll encounter when using the Convore platform.

Provider

Providers are the third-party services like Gmail, Outlook, Twilio, Sendgrid, etc., that you connect with Convore. Convore doesn’t replace these services but works alongside them to help you build your messaging experience.

Connector

A connector in Convore serves as a bridge, allowing your application to interact with various Providers.

For those looking to get started quickly, Convore provides ready-to-use connectors that simplify testing and speed up the initial setup process.

Additionally, you have the option to create custom connectors. These are designed to securely hold provider settings, such as the client_id and client_secret associated with the provider’s authentication application.

Channel

A channel in Convore is a specific route for sending and receiving messages. It could be an email, SMS, or chat, each with its unique features and capabilities.

A channel is closely linked with connectors. The connector sets up the connection with the service provider, and the channel uses this connection to manage the exchange of messages.

For example, a specific user’s email account can be a channel. Conversations take place within these channels, with each conversation being a series of messages exchanged between parties.

Conversation

Conversations in Convore represent communication threads. They consist of messages that carry the actual content of the conversation.

For example, if you receive a new email from a customer, this email thread is considered a conversation. The contents of the email sent by the customer constitute the first message in the conversation. When you respond to the customer, you add a second message to the conversation.

Message

Messages are the building blocks of a conversation in Convore. They represent the actual content of the conversation, which could be email responses, text message content, and so on.

To illustrate, let’s consider a scenario where a customer initiates an email conversation via Gmail. When Convore receives this email, it creates a new conversation. The email sent by the customer is considered the first message in this new conversation.

When your application or AI agent responds to this email using Convore’s API, it generates a second message in the conversation. This response is then delivered to the customer through Gmail.

If the customer replies to the AI agent’s response, their reply is received by Convore and becomes the third message in the conversation. This back-and-forth exchange of messages forms the entirety of the conversation on Convore.