9.1: Common Questions
You're not alone! Here are the questions we hear most often, with clear, practical answers.
9.1.1: "What If My Agent Gives Wrong Answers?"
This is one of the most common concerns, and it's usually an easy fix!
The Quick Fix
Your agent's knowledge comes from two places:
- Knowledge Base - Documents you've uploaded
- Instructions - What you told the agent to do
When answers are wrong, one of these is usually outdated.
Fixing Wrong Answers
"My agent is giving incorrect information about our return policy. It says we accept returns within 14 days, but our actual policy is 30 days."
Navigate to your AI column → Settings → Knowledge Base
Delete old policy → Upload current version
Check that instructions don't contradict your knowledge base
✅ "Always check the knowledge base for our current return policy"
Add a new row and ask: "What's your return policy?"
Set a reminder to review and update your knowledge base quarterly. When policies change, update the knowledge base the same day!
💡 ✅ Best Practice
Set a calendar reminder to review your knowledge base every quarter. When company policies change, update the knowledge base immediately!
Give Your Agent Examples
Sometimes your agent needs to see examples of good responses. Add a few sample conversations to your instructions:
Example for tone:
Customer: "What are your hours?"
Good response: "We're here Monday-Friday, 9am-6pm EST. Need help outside these hours? Email us anytime at support@example.com!"This teaches your agent not just what to say, but how to say it.
9.1.2: "How Do I Make My Agent Faster or Slower?"
Good news: You don't need to control speed manually!
How Speed Works
Your automation runs automatically as soon as:
- All required data is available
- Any dependencies are completed
- Rate limits allow (if you set them)
Think of it like a conveyor belt - items move forward as soon as they're ready.
💡 💡 Think of It Like This
Imagine cooking breakfast:
- Toast pops up when it's ready
- Coffee brews when water is hot
- Eggs cook when pan is heated
You don't manually control timing - things happen when conditions are met!
When You DO Want to Control Timing
Use Case 1: Schedule for specific times
- Example: "Send summary email every Monday at 9am"
- Solution: Use a Schedule trigger (daily, weekly, monthly)
Use Case 2: Slow down to avoid overwhelming APIs
- Example: "Don't call the external API more than 100 times per hour"
- Solution: Add rate limits to your column (see Section 8.2 of the Reference Guide)
Use Case 3: Delay before action
- Example: "Wait 24 hours after ticket closed before asking for feedback"
- Solution: Add time-based conditions to your columns
9.1.3: "Can I Undo Something?"
You have several safety options!
What You Can Undo
✅ Clear and Re-run Individual Cells
- Right-click any cell
- Select "Clear Cell"
- The column will automatically re-run for that row
This is perfect for fixing one-off mistakes!
✅ Edit Data in Manual Columns
- Any column you manually type into can be edited anytime
- Just click the cell and change the value
- No special undo needed - it's like editing a spreadsheet
✅ Revert Taible Configuration
- If you messed up column settings, export your taible first (see below)
- Then you can always re-import the old version
What You Can't Undo (Be Careful!)
❌ Deleting a taible - This is permanent! ❌ Deleting rows - Gone forever ❌ Actions that happen outside Taibles - Like sending emails or updating external systems
💡 ⚠️ Before Major Changes
Always export your taible first!
This gives you a backup you can restore if something goes wrong. See "How to Make a Backup" below.
9.1.4: "How Much Does It Cost?"
Taibles uses a credit-based system. Different actions cost different amounts of credits.
Understanding Costs
Common operations and their costs:
- AI responses: 1-10 credits depending on length and complexity
- HTTP requests: 1 credit per call
- Data storage: Minimal cost, included in base plan
- Email sending: 1 credit per email
Your exact pricing depends on your plan. Check your dashboard to see:
- Current credit balance
- Credits used this month
- Cost per action type
💡 📊 Monitor Your Usage
Go to Settings → Usage History to see exactly what's using credits. This helps you identify opportunities to optimize!
Cost Optimization Tips
1. Use rate limits to control spending
- Limit expensive API calls to X per hour
- Prevents runaway costs if something loops
2. Cache results when possible
- Don't look up the same information repeatedly
- Store results in your taible and reference them
3. Use conditions wisely
- Only run expensive operations when needed
- Example: Only enrich leads with score > 50
4. Review usage monthly
- Look for unexpected spikes
- Identify automations using more credits than expected
9.1.5: "What If an Integration Doesn't Work?"
Integration issues usually fall into three categories, each with a clear fix.
Integration Not Working?
- Trigger is enabled
- Correct account selected
- Right channels/folders monitored
If you've tried all steps above and it's still not working:
- • Check the service's status page (e.g., status.slack.com)
- • Try disconnecting and reconnecting the account completely
- • Contact support with screenshots of your configuration
Common Issues by Integration Type
Email Issues:
- Check that you've enabled IMAP/SMTP in your email provider
- Gmail users: Enable "Less secure app access" or use App Password
- Verify the email address in your trigger matches your inbox
Slack Issues:
- Re-authorize the Slack app in your workspace settings
- Make sure the bot is invited to the channel you're monitoring
- Check that workspace admin approved the integration
WhatsApp Issues:
- Verify your WhatsApp Business account is active
- Check webhook URL is correctly configured in WhatsApp settings
- Ensure phone number verification is complete
9.1.6: "Can Multiple People Work on the Same Taible?"
Yes! Taibles is built for teams.
Real-Time Collaboration
Taibles supports real-time collaboration. Your team can view and edit the same taible simultaneously, just like Google Docs.
When a teammate adds a row, edits a cell, or changes a column configuration, you'll see the update immediately in your browser. No need to refresh!
If two people try to save changes to the same taible configuration at once, Taibles prevents one person from overwriting the other's work.
Perfect for teams handling customer support tickets, processing leads, or reviewing content. Everyone can work on different rows at the same time.
All three see each other's changes instantly. No stepping on each other's toes!
Collaboration Tips
Assign work clearly
- Use an "Assigned To" column to show who's working on what
- Filter your view to show only your assigned items
- This prevents duplicate work
Communicate about configuration changes
- If you're changing column settings, let your team know
- Consider cloning the taible to test changes first
- Keep a changelog in a "Notes" column
Use saved views
- Create personal views for your workflow
- Share team views for common filters
- Everyone can have their own perspective on the same data
9.1.7: "How Do I Make a Backup?"
Two ways to protect your work: Export and Clone.
Method 1: Export (For Backups and Sharing)
What it does: Downloads your taible as a .agent file
When to use:
- Before making major changes
- To share with another organization
- Monthly backups for peace of mind
How to do it:
Export Taible
Lead Enrichment Pipeline
Automatically enrich leads with company data and contact information
When enabled, all existing data will be included in the export file. When disabled, only the taible structure will be exported.
Options when exporting:
- Include data: Your backup includes all rows (larger file)
- Structure only: Just the configuration, no data (smaller file)
Keep exported files in a safe place like Google Drive or Dropbox!
Method 2: Clone (For Testing)
What it does: Creates an instant duplicate of your taible
When to use:
- Testing new column configurations safely
- Creating a development version
- Trying experimental changes
How to do it:
Clone Taible
Lead Enrichment Pipeline
Automatically enrich leads with company data and contact information
When enabled, all existing data will be copied to the cloned taible. When disabled, only the structure will be cloned.
💡 ✅ Pro Tip: Test in a Clone
Always test major changes in a cloned taible first!
- Clone your production taible
- Make changes in the clone
- Test thoroughly
- Apply changes to production once verified
This prevents breaking your live automation!
What You've Learned
You now have answers to the most common questions:
✅ Fixing wrong answers - Update knowledge base and instructions ✅ Understanding speed - Automatic execution, rate limits for control ✅ Undoing mistakes - Clear cells, edit data, export for safety ✅ Managing costs - Monitor usage, optimize with rate limits ✅ Fixing integrations - Check connections, permissions, configuration ✅ Collaborating with teams - Real-time updates, no conflicts ✅ Making backups - Export files, clone for testing
These answers solve 90% of the problems you'll encounter. For everything else, the User Reference has deep technical details!
Quick Reference: Where to Find Help
For troubleshooting specific issues:
- Reference Section 16.2: Common Issues and Solutions
- Reference Section 11.2: Debugging Workflow
For collaboration details:
- Reference Section 13.1: Multi-User Scenarios
- Reference Section 13.2: Version Control
For cost management:
- Reference Section 8.2: Configuring Rate Limits
- Reference Section 15.1: Real-Time Monitoring
For integration help:
- Reference Section 10.5: Integration Patterns
- Each connection type has detailed setup guides
Previous: 8.5 Content Publishing CalendarNext: 9.2 Tips for Success