# Best practices using Kustomer Architect

> This best practices guide helps teams use the AI Setup Assistant to configure Kustomer quickly and safely   Before you start   First determine how you plan to

Source: https://help.kustomer.com/en_us/best-practices-using-the-ai-setup-assistant-ryBonVGvZx

Last updated: 2026-06-01T14:29:17.193Z

This best practices guide helps teams use Kustomer Architect to configure Kustomer quickly. 

## Before you start

**First, determine how you plan to configure your org.** 

*   **Full org setup:** Say “set up my organization” to run a comprehensive guided setup. Best if you're completely new to Kustomer, and do not have an existing CX platform setup you can import from. 
    
*   **Targeted setup:** Say commands like “create a klass” or “add custom attributes” for specific tasks. Best when you've already done some work, but you want to fully customize Kustomer to fit your needs. 
    
*   **Migration:** Tell the assistant your current platform (only Zendesk is supported at this time) to import configuration and speed migration.
    
    *   **Gather platform credentials (migration only).**
        
        *   Prepare API tokens, subdomains, or admin credentials.
            
        *   Use the secure credential form the assistant provides — do not paste credentials into chat.
            

## Common pitfalls

*   **Do not type credentials in chat.** Always use the secure form.
    
*   **Don’t skip org analysis for full setups.** Skipping lowers recommendation quality.
    

## During setup

Remember to share industry, channels, team structure, volume, pain points, and automation goals up front to get tailored suggestions.

#### **Let the Architect handle the manual labor.**

*   The Architect pre-fills forms using your business model and industry. 
    
*   Review targeted suggestions and adjust in real time rather than rebuilding from scratch.
    
*   Clickable option cards and forms help reduce errors.
    
*   Use the resource links generated by the Architect to rapidly confirm changes made. 
    

#### **Configure bulk actions using conversational language.**

*   Use buttons such as **Create all teams** or **Create all tags** to apply multiple changes at once.
    
*   The assistant checks for existing resources and skips duplicates automatically; you can deselect individual items before applying.
    

#### **Try to follow the Architect's natural flow.**

*   The Architect runs: **org analysis → business model → platform detection → configuration → data profile → setup plan**.
    
*   Don’t skip steps: each adds context that improves recommendations.
    
*   It's safe to iterate over time. The Architect will recall your configurations, and you can perform audits any time you wish. 
    

## What Kustomer Architect can and can’t do

#### **Manual steps you’ll still need to handle.**

*   User management and permission changes happen outside the assistant.
    
*   Some integrations (for example, payment processors, Shopify, or other apps) require manual installation and configuration.
    
*   Rolling back changes you've asked the Architect to make. Some changes require a manual rollback. 
    

#### **What the Architect can fully automate.**

*   Klasses and custom attributes.
    
*   Tags, shortcuts, and business schedules.
    
*   Brands and channel configuration for email, chat, and SMS.
    
*   Workflows (via WorkflowExpert integration).
    

## Post-setup checklist

**Remember to test your setup, especially as you configure it.**

*   Send a test email to the configured addresses.
    
*   Open the chat widget in an incognito window and create a test conversation.
    
*   Confirm custom attributes and tags appear as expected in conversations and profiles.
    

#### **Clean up unused attributes and objects.**

*   Ask the Architect to delete items explicitly (for example: “Delete the VIP tag”).
    
*   Ask the Architect to disable unused custom attributes it has created.
    

## Pro tips

**Have an existing configuration? Leverage platform import to migrate it.**

*   Importing from Zendesk (and soon other platforms) is faster and more accurate than  manually describing configurations.
    
*   Review the import summary carefully before mass-creating resources.
    

**Create workflows early and experiment often.**

*   Start with simple automations: auto-close, auto-tagging, and basic routing.
    
*   Workflows deliver immediate time savings and reduce manual triage.