> This page is part of the [Customer.io documentation](https://docs.customer.io). For the complete index, see [llms.txt](https://docs.customer.io/llms.txt). > Last updated: September 1, 2026 > To take actions in Customer.io from an agent, use the [Customer.io CLI](https://docs.customer.io/ai/cli/get-started.md) or the [MCP server](https://docs.customer.io/ai/mcp/get-started.md). # Introduction to messaging Welcome to Customer.io! This page and section are designed to help you get acquainted to our platform. This page introduces the core concepts in Customer.io, and the following pages dive deeper into each concept. Customer.io incorporates data from your customer touchpoints, helping you customize automations and send sophisticated, personalized messages that support and engage your audience. New here? Check out our Quick Start Guide This section provides an overview of Customer.io. But we recommend using our [Quick Start Guide](/get-started/quick-start-guide/) if you’re ready to jump in and start using Customer.io. ## How it all works The image below illustrates what a well-rounded integration with Customer.io looks like. ![](https://docs.customer.io/images/cio_integration_visualization.svg) 1. **Your Product** sends **Real-time Data** to [Customer.io](/get-started/integrate/#integrate-with-customerio). 2. We’ll associate your real-time data with **Profiles** and **Objects**. *Profiles* are your leads, users, customers, etc that you want to send messages to. *Objects* are things that are important to your users, like an account they belong to. 3. Next, you **Activate your data**: populate **Segments** and build powerful automations that send personalized **Messages** to your audience. When you’re fully set up, data will flow into Customer.io, triggering automations and messages, helping you automate customer communications! Want to send customer activity to your workspace? Check out our [Get Started guide](/get-started/integrate/) to learn more about integration methods. ## Profiles In Customer.io, everything revolves around profiles. You represent a profile with data: * the things you know about them ([attributes](/journeys/people/manage/attributes/)) * the things they do ([events](/journeys/people/events/)) * the things they’re related to ([object](/journeys/objects-data/objects/) relationships) * the automations they’re in and the messages they’ve received You’ll find profiles and their associated data on the **Profiles** page. ## Objects Objects are the things that are important to your profiles, like an account they belong to, online courses they enroll in, or homes they’re interested in purchasing. A change to object and profile relationships can trigger automations. You’ll find objects under *Manage audience* in the left-hand menu. Learn more about setting up objects here: [Objects: how they work](/messaging/objects-data/objects/start/). ## Segments Segments are groups of profiles that match the same criteria. A segment can trigger automations, define recipient lists, represent conversion criteria, and more. To help you get started, we’ve pre-configured a few segments for you. If you go to the **Segments** page, you’ll see segments like “Paying Customers”, “Have not logged in recently” and “Unsubscribed”. Be sure to check those out! Learn more about segmenting your users here: [Getting Started: Segments](/get-started/segments-and-profiles-data/) ## Automations, Broadcasts, and Transactional Messages Automations and Broadcasts send email, SMS, push, and in-app messages to your profiles. But, beyond that, your automation and broadcast workflows can send Slack messages, webhooks, update [attributes](/journeys/people/manage/attributes/), and more. Transactional messages are emails that you send in response to your audience’s actions in your app. **Automations** are the quintessential messaging automation workflow. They help you send one or more messages in a workflow sequence to profiles when they meet your trigger condition(s). You can trigger automations when profiles perform events, when they join Segments (e.g. they meet attribute conditions), and so on. Automations are ideal for dripping content to profiles as they become eligible to receive it. * Welcome and onboarding series * Re-engagement series * Behavioral messages (respond to actions profiles take in your app or on your website) **Broadcasts** send a message to a list of recipients. Broadcast messages are queued to send to all the defined recipients at a time you specify. Broadcasts are ideal for manually sending messages or programmatically triggering announcements in bulk, like: * One-time send messages * Pre-scheduled announcements * Promotions * Periodic release notes * Community alerts * Event change notifications * Product launches **Transactional messages** help you respond directly to your audience’s actions in your app. Unlike broadcasts and automations, transactional messages are one-to-one interactions. Transactional messages are ideal for: * Purchase receipts * Registration confirmations * Password resets * Event reminders * Shipping updates Learn more about [Automations and Broadcasts](/get-started/send-messages/) or [Transactional Messages](/messaging/send/transactional/api/). ## Integrations Once you grasp the basics of Customer.io, you’ll want to plan your integration. And don’t worry - you can also use your preferred tools and sources to transit data through Customer.io. It’s up to you! ©2026 Peaberry Software, Inc. [Status](https://status.customerio.com/) [Terms of Service](https://customer.io/legal/terms-of-service/) [Privacy Policy](https://customer.io/legal/privacy-policy/) [](https://www.linkedin.com/company/customer-io)[](https://twitter.com/customerio)[](https://www.youtube.com/channel/UCkCaWdezRoa8ZyR9pEVaipA)[](https://www.instagram.com/customer.io/)