Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.penbox.io/llms.txt

Use this file to discover all available pages before exploring further.

Penbox uses a credit-based system to measure and bill resource consumption across your organization. Activities such as collecting electronic signatures, running automations, utilizing Penbox Intelligence, and generating documents all draw from a shared pool of workspace credits.

​
Credit Pooling

Credits are managed entirely at the workspace level. They are not tied to individual users. Each seat in your workspace includes a dedicated credit allotment. These credits compound at the workspace level, creating a single, shared pool that any member or automation in the workspace can draw from.
Because credits are pooled, individual team members do not have personal limits. All resource consumption is consolidated, making it easy to manage usage and scale your operations.

​
Credit Renewal

Your credit allotment resets automatically every month depending on your plan type:
  • Monthly plans: Credits renew on your monthly billing date.
  • Annual plans: Credits renew each month on the same date as your annual billing date (for example, if your annual plan started on October 15, your credits will renew on the 15th of every month).
Unused credits do not roll over to the next billing cycle.

​
Top-Ups and Extra Credits

If your workspace runs low on credits before your next renewal date, you can buy extra credit packages. To purchase additional credit packs, contact your Account Manager directly.

​
Action Consumption Rates

Credits are consumed dynamically as your workspace executes actions. Penbox maps credits directly to specific, discrete actions, ensuring you only pay for what you run.

​
Forms

You are not billed when sending forms. Instead, Penbox only consumes credits when a form is effectively activated by the recipient:
  • Started Form: When a recipient begins interacting with a form (meaning they actively start filling in information or entering data), it consumes 50 credits. This is a one-time charge per request, triggered only when data entry is initiated, rather than when the form is sent or simply opened.

​
Penbox Intelligence

AI-powered parsing, analysis, and validation use credits based on the volume processed:
  • Document Intelligence: Extracting and analyzing structured data from uploaded documents consumes 3 credits per page processed by the LLM.
  • Email Intelligence: Processing inbound communications, such as auto-triaging with Case-inbound or organizing with Labelize, consumes 2 credits per execution.
  • Penbox Agent: Because the Penbox Agent is currently in beta, interacting with it does not consume any credits. This policy is temporary and is subject to change when the Penbox Agent transitions out of beta.

​
Automations and Communications

Standard automation runs and background communication tasks consume credits as they execute:
  • Automation (non-AI): Triggering and executing any standard, non-AI workflow or automated step consumes 1 credit. This includes operations such as automated reminders, automatic step triggering, automatic status transitions, and automated API calls.
  • SMS Notifications: Sending text messages to recipients consumes 4 credits per SMS part (each segment of up to 160 characters). Longer messages that span multiple parts will consume credits for each individual part sent.

​
Document Generation

Creating documents directly from form data or case inputs is billed per file:
  • Document Generation: Generating a PDF, DOCX, or other supported file formats consumes 20 credits.

​
Electronic Signatures

Collecting signatures is billed per transaction:
  • Signature Execution: Completing a signature request consumes 65 credits. This covers standard signature methods, including those initiated via SMS, Email, Handwritten, or ID-card verification.
  • Advanced Signature Providers: Using Itsme and Swisscom signature types consumes the base 65 credits and incurs an additional provider surcharge, which is billed separately.

​
Integrations

Connecting and syncing data with external third-party systems is billed according to system interactions:
  • Brio Transactions: Interacting with Brio consumes 3 credits per unique object within a rolling 24-hour window. For example, any number of read or write operations performed on a single claim object within the same day only consumes 3 credits total. However, if a workflow interacts with multiple distinct objects, such as updating a claim and a separate contact, each unique object is billed separately at 3 credits.