[null,null,["最后更新时间 (UTC):2025-03-11。"],[[["\u003cp\u003eRBM agents are programmatic entities that brands use to send messages to users, offering interactions ranging from simple notifications to complex, conversational exchanges within messaging apps.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating an RBM agent, you can define the agent's name, branding, and other information to identify it in user conversations, and determine whether the agent should handle all departments or specific ones.\u003c/p\u003e\n"],["\u003cp\u003eRBM agents are assigned to one of three regions (North America, Europe, or Asia Pacific), which determines where the agent operates and stores data, and this choice is permanent.\u003c/p\u003e\n"],["\u003cp\u003eAgents are also categorized by billing type (Conversational, Basic Message, or Single Message) and use case (OTP, Transactional, Promotional, or Multi-use), each impacting how the agent interacts with users, and billing can only be changed before launching, and use case cannot be changed after launch.\u003c/p\u003e\n"],["\u003cp\u003eAgents are created and managed through the Business Communications Developer Console or the Business Communications API, which allows for the customization of the agent, submission for launch, and also highlights that they cannot be deleted for security reasons.\u003c/p\u003e\n"]]],[],null,["# Create an agent\n\n| **Agent** A programmatic entity that sends messages to users on behalf of a brand. The agent includes any interface that users interact with and any code or infrastructure required to power the interaction. Agents can provide a simple one-way experience, like sending a notification, or they can be conversational and react to users' responses in a back-and-forth exchange.\n\nIn an RBM conversation, messages between a user and an agent appear in an\nRCS-enabled messaging app, such as iMessage or Google Messages, on the user's\ndevice. The messaging app displays branding and profile information for your\nagent, including name, logo, description, contact information, and URLs.\n\nYou could create a single agent for *Growing Tree Bank* that allows users to\ninteract with various departments like Customer Care and Mortgages.\nAlternatively, you could create separate agents for each department, such as\n*Growing Tree Bank Customer Care* and *Growing Tree Bank Mortgages*.\n\nBefore creating multiple agents for one business, consider the user experience\nand refer to the\n[conversational best practices](/business-communications/rcs-business-messaging/guides/learn/best-practices#conversational-ui).\n\nCreate your agent\n-----------------\n\nRBM agents use the [RCS Business Messaging API](/business-communications/rcs-business-messaging/reference/rest)\nto send messages, events, and other requests to users. When you create an agent,\nyou enable access to the RBM API and\n[define your agent's colors and branding information](/business-communications/rcs-business-messaging/guides/build/agents/edit-agent-information#edit_your_agents_information).\n\nThe following steps describe how to create an agent with the\n[Business Communications Developer Console](https://business-communications.cloud.google.com/console/partner-console).\nYou can also create an agent with the\n[Business Communications API](/business-communications/rcs-business-messaging/reference/business-communications/rest/v1/brands.agents/create).\n\nTo create an agent:\n\n1. Go to the [Business Communications Developer Console](https://business-communications.cloud.google.com/console/partner-console) and sign in with your RBM partner Google Account.\n2. On the homepage, click **+ Create agent**.\n3. In the **New RCS Business Messaging agent** window, specify the following information:\n - Brand that your agent represents\n - Agent name\n - [Hosting region](#region)\n - [Billing category](#billingCategory)\n - [Use case](#usecase)\n4. Click **Create agent**.\n\nOnce an agent is created, you can access all the features of the\n[Business Communications Developer Console](https://business-communications.cloud.google.com/console/partner-console)\nto\n[edit your agent's information](/business-communications/rcs-business-messaging/guides/build/agents/edit-agent-information#edit_your_agents_information)\nand submit it for launch. To start, select your agent from the homepage.\n\nNote that deleting an RBM agent is not permitted for security reasons. Email\n[rbm-support@google.com](mailto:rbm-support@google.com) if you need assistance.\n\n### Identify the agent's region\n\nRBM agents can exist in one of three regions: North America, Europe, and Asia\nPacific. The RBM API supports\n[three regional endpoints](/business-communications/rcs-business-messaging/guides/learn/best-practices#regional-endpoints)\nto help businesses comply with regional and business requirements.\n\nWhen you create your agent, choose your agent's region based on the applicable\nregulations, requirements, and proximity to end users. This region determines\nwhere your agent operates from and where it stores its data.\n\nIf you or your intended users don't fit within those regions, choose the region\nthat is closest to you to minimize latency. For example:\n\n- If you're in Latin America, choose the North America region.\n- If you're in Africa, choose the Europe region.\n- If you're in Australia, choose the Asia Pacific region.\n\nDon't decide your agent's region based on your target carriers. All regions\nhave equal access to carriers worldwide.\n| **Note:** You can't change your agent's region after you create your agent.\n\n### Determine the agent's billing category\n\nWhen creating an RBM agent, you need to specify its billing category based on\nhow the agent will interact with users. Choose the category that most closely\nmatches your agent's intended behavior:\n\n- **Conversational**: For agents that engage in multi-turn conversations with users.\n- **Basic Message or Single Message**: For agents who send messages without expecting frequent replies.\n\n| **Note:** The two non-conversational billing categories, Basic Message and Single Message, work exactly the same way. This is a bit of a historical quirk that we're working to simplify. For now, feel free to use either category for your non-conversational messages --- whether they're plain texts or rich cards. You'll be billed the standard non-conversational rate. For more information, see [Agent billing categories](/business-communications/rcs-business-messaging/carriers/reports#agent-billing-categories).\n\nYou can only change your agent's billing category before launching it. Email [rbm-support@google.com](mailto:rbm-support@google.com)\nif you need to change the billing category after launch.\n\nFor more information about the RBM billing model, refer to the [RBM billing FAQ](/business-communications/rcs-business-messaging/guides/learn/rbm-billing-faq).\n\n### Identify the agent's use case\n\nEach RBM agent is required to have a predefined use case. This helps categorize\nyour agent and apply the right\n[business rules](/business-communications/rcs-business-messaging/guides/learn/agent-use-cases#businessrules)\nfor a good user experience. RBM supports four use cases:\n\n- **OTP**: One-time passwords required to securely authenticate an account or confirm a transaction.\n- **Transactional**: Notifications, updates, or alerts that share information directly relevant to a customer's existing services or products, such as alerts for suspicious account activities, purchase confirmations, and shipping notifications.\n- **Promotional**: Sales, marketing, and promotional messages to new or existing customers, with the goal of increasing awareness, engagement, and sales.\n- **Multi-use**: Conversations that combine transactional and promotional messages, such as sending an account notification followed by a discount offer or upgrading to a new product or service.\n\nEach use case has different rules about what you can send. To learn more about\neach use case and find the best fit for your agent, see\n[Choose the right use case for your agent](/business-communications/rcs-business-messaging/guides/learn/agent-use-cases#choose_the_right_use_case_for_your_agent).\n\nOnce you submit your agent for launch, you cannot change the use case. Check\nyour\n[country's use cases and business rules](/business-communications/rcs-business-messaging/guides/learn/agent-use-cases#businessrules)\nbefore submitting your agent.\n\n### Next steps\n\nNow that you have a working agent, you can\n[edit agent information](/business-communications/rcs-business-messaging/guides/build/agents/edit-agent-information#edit_your_agents_information)\nand\n[configure an agent-level webhook](/business-communications/rcs-business-messaging/guides/integrate/webhooks)\nif needed.\n\nRemember that you need a service account key to securely authenticate API calls.\nIf you haven't already created a [service account key for your partner account](/business-communications/rcs-business-messaging/guides/get-started/partner-account#set_up_service_account_to_authenticate_api_calls),\nnow is the time to do it."]]