Onboarding Overview
Getting Lucidis up and running typically takes 2-4 weeks, depending on complexity. Here's what you'll need to provide.
Phase 1: Discovery (Week 1)
Define Your Use Cases
Identify the workflows you want to automate:
- What requests are most common?
- What data needs to be accessed?
- What actions should Lucidis take?
- What requires human approval?
Map Your Data Sources
Document where information lives:
- CRM and customer databases
- Order management systems
- Knowledge bases and documentation
- Spreadsheets and data warehouses
Phase 2: Setup (Week 2)
Connect Your Channels
Provide access to communication platforms:
- Email domains and inbox credentials
- Chat platform API keys (Slack, Teams, etc.)
- SMS provider credentials (Twilio, etc.)
- Web form endpoints
Connect Your Data
Set up integrations to your systems:
- API credentials or database connection strings
- OAuth connections to SaaS tools
- Read/write permissions configuration
- Test credentials for staging environment
Define Your Rules
Configure how Lucidis operates:
- Business hours and availability
- Approval workflows and thresholds
- Routing rules for complex requests
- Access controls and permissions
Phase 3: Configuration (Week 2-3)
Knowledge Base Setup
Provide information Lucidis needs:
- Common questions and answers
- Product documentation
- Policy documents
- Process workflows
Action Configuration
Define what Lucidis can do:
- Which actions are allowed
- What requires approval
- Maximum values (e.g., refund limits)
- Escalation criteria
Response Templates
Customize how Lucidis communicates:
- Brand voice and tone guidelines
- Response templates for common scenarios
- Signature and footer content
- Error messages and fallbacks
Phase 4: Testing (Week 3-4)
Controlled Testing
Start with limited scope:
- Test with internal team members first
- Run in parallel with existing processes
- Review all interactions closely
- Refine rules and responses
Gradual Rollout
Expand carefully:
- Start with low-risk use cases
- Increase automation percentage over time
- Monitor performance metrics
- Adjust based on learnings
What You Need to Provide
Access & Credentials
- [ ] Channel access (email, chat, etc.)
- [ ] Data source credentials
- [ ] API keys for integrations
- [ ] SSO configuration (if applicable)
Business Information
- [ ] Common request types and workflows
- [ ] Business rules and policies
- [ ] Approval hierarchies
- [ ] Brand voice guidelines
Team Resources
- [ ] Technical point of contact
- [ ] Business owner for each use case
- [ ] Approvers for sensitive actions
- [ ] QA reviewers during testing
Documentation
- [ ] FAQ and knowledge base content
- [ ] Process documentation
- [ ] Product/service information
- [ ] Customer communication examples
Ongoing Support
After launch, you'll have:
- Dedicated success manager
- Technical support channel
- Regular performance reviews
- Continuous optimization recommendations