• Tokens: Units of text where 1 token is roughly 4 characters. For example, 100,000 tokens are approximately 400,000 characters or 400 kilobytes (KB) of text data.

• File Size Comparison:
  • 100,000 Tokens ≈ 400 KB (approx. 400,000 characters)
  • 2 Million Tokens ≈ 8 MB (approx. 8 million characters)
  • 5 Million Tokens ≈ 20 MB (approx. 20 million characters)

Usage Breakdown:

• File Uploads:
  • Suppose the restaurant uploads a menu file of 1 MB (approximately 1 million characters or 250,000 tokens).
  • This leaves 1.75 million tokens (7 MB) for messaging and other interactions.
• Messaging Usage:
  • The remaining 1.75 million tokens can be used for customer interactions such as reservation queries, menu questions, and special promotions.
  • If each message averages 1000 characters (250 tokens), the restaurant can handle approximately 7,000 messages per month.
• Daily Usage:
  • Over a 30-day month, the restaurant can process about 233 messages per day (7,000 messages / 30 days).
  • This is a suitable volume for a busy restaurant handling daily customer inquiries and interactions efficiently.

This example shows how the Basic plan's token allocation translates into practical usage for a busy restaurant, balancing between file uploads and message processing.