---
schema_version: "1"
id: 24bef23ea38c0b452bbfba7289120c238249853440f22c743253e2beb5dc7f8b
title: Best Practices for Asynchronous Components
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/bots_service_enhanced_async_best_practices.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.bots_service_enhanced_async_best_practices.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 85d527578fc834540bb2dce2f75a0eebd555297827aabe84cf248cc4c8e731b2
description: Customers don’t have to respond to asynchronous components right away. When you add an asynchronous component to a bot conversation, carefully consider your conversation design to gracefully handle errors and changes in context.
products:
  - Service Cloud
  - Service Intelligence
release: "264"
---
# Best Practices for Asynchronous Components

Customers don’t have to respond to asynchronous components right away. When you add an asynchronous component to a bot conversation, carefully consider your conversation design to gracefully handle errors and changes in context.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.einstein_service_intro.htm&amp;language=en_US" target="_blank">View supported editions</a> for Einstein Bots.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.messaging_editions.htm&amp;language=en_US" target="_blank">View supported editions</a> for Messaging.</td></tr></tbody></table>

- **[Conversation Design for Asynchronous Components](https://help.salesforce.com/s/articleView?id=service.bots_service_enhanced_async_conversation.htm&release=264.0.0&type=5)**  
    Because customers don’t have to respond to asynchronous components right away, these components require careful conversation design. Use asynchronous component settings and Rule conditions and actions to ensure a natural conversational experience.
- **[Error Handling for Asynchronous Components](https://help.salesforce.com/s/articleView?id=service.bots_service_enhanced_async_errors.htm&release=264.0.0&type=5)**  
    Asynchronous components include an optional error variable to give you more control over how to handle specific errors. Use an Apex class and Rule actions to customize the behavior of the Error Handler dialog based on the error variable. For example, when a customer attempts to respond to an expired authentication request, you can prompt the user to try again with a new authentication request.