Service Management

Services define what clients purchase and the work they can request. A service can be a one-time purchase or a recurring subscription, with fixed, hour-based, or credit-based allowances.

Access

Open Services in the team navigation. Permissions are view_services, create_services, edit_services, and delete_services. Some pricing and delivery features also require plan access.

Create a service

1. Choose Create Service and select One-time or Recurring.
2. Add a name, description, and optional cover image or video URL.
3. Configure pricing and request allowances.
4. Build the form clients fill out for the service.
5. Add FAQs if useful, review the configuration, and save as a draft or publish.

The name is required even for a draft. Drafts allow you to finish configuration before making a service available. Cover images support JPEG, PNG, and GIF, up to 50 MB.

Pricing and allowances

Standard

Set a currency price and the number of requests included. This works for fixed deliverables and packages.

Time-based

Set a currency price and hours included. Requests consume the organization's available hour allowance according to the service's request allocation. Hour-based services require the relevant plan feature.

Credit-based

Set a currency price and credits included. These credits become an allowance clients can use for requests. Credit-based services require the relevant plan feature.

The service's purchase price and the allowance it grants are separate settings. For example, a currency-priced package can include a number of credits; the Credits field is not simply a second currency price. See Credits for balances and consumption.

Recurring pricing

Add pricing tiers for the billing periods you offer. Available tier periods include weekly, monthly, quarterly, twice yearly, and annually. Each tier has a price and can include hours or credits for the selected pricing model.

Recurring settings include a trial period, request limits, maximum concurrent requests, and rollover of unused hours or credits where applicable. Check these settings before publishing a subscription offer.

Request allocation and quantity

Choose fixed request allocation, hours-based allocation, or credits-based allocation where available. Set the included request count or allowance, purchase limits, and concurrent request limits as appropriate.

For services that support buying more than one unit, enable quantity selection and set a maximum quantity per purchase. Purchase quantity and concurrent request limits serve different purposes: one controls the purchase, the other controls ongoing work.

Client form and FAQs

Configure the title field and the additional information clients should provide. Supported field types include text, textarea, rich text, file upload, select, checkbox, radio, and signature.

Set labels, required fields, placeholders, and options as needed. Use conditions to show or hide a target field when another field contains, equals, or does not equal a value. Add FAQs in the final step to explain scope, requirements, or delivery expectations.

Test the form with a realistic client brief, including any required fields, conditions, files, and signatures.

Turnaround and deliveries

When your plan includes SLA tracking, set Turnaround Hours to define the service's target turnaround.

When versioned proofing is available, enable deliveries and configure included revisions. Delivery and approval controls then appear on eligible requests. A revision allowance helps track rounds of feedback; review the request's delivery history when managing scope. See Deliveries & Approvals and Capacity & SLA.

Automatically create recurring requests

On eligible plans, enable the recurring service's automatic request option in its advanced settings. Successful subscription renewals can then create a new request for the client.

The generated request is free of charge because the subscription renewal has already been billed. It does not copy answers or uploaded files from an earlier request. Collect a fresh brief from the client when each renewal needs different requirements.

Publish and share

A published, active service can be available for checkout. Enable Show in Catalog if it should also appear in the catalog. A service hidden from the catalog can still be shared through its direct checkout link when otherwise available.

Use the service's copy-link action to get the correct workspace or custom-domain URL. The public checkout path is /services/checkout/{service-slug}. See Service Catalog and Order Forms for other purchasing flows.

Manage existing services

Open a service to review its configuration. You can edit it, duplicate it, toggle its active status, set a default service, publish it, or move it back to draft. The service list also provides bulk actions.

Use draft status for unfinished offers and inactive status to stop offering a service. Review existing subscription arrangements before changing an offer's pricing or availability.

Deleting a service moves it to the recycle bin rather than immediately destroying it. Restore it when needed or use permanent deletion only when you are sure it is no longer required. Permanent deletion cannot be undone. See Archive & Recovery.

Troubleshooting

• Service missing from catalog: Check published status, active status, and Show in Catalog.
• Credit or hour pricing unavailable: Check the corresponding feature in your plan.
• Client cannot submit a request: Check their organization's purchases, remaining allowance, and concurrent limits.
• Automatic renewal request missing: Check the service option, plan access, and whether the renewal payment succeeded.
• Form validation fails: Check required fields, conditional visibility, file restrictions, and signature requirements.