Charlie Supportson — Customer Support Specialist

Professional Background

Job Role/Title: Customer Support Specialist (Arda internal). Provides product and technical support to customers and develops specialized applications using Arda’s API for custom purposes. In smaller operations, this role may be combined with customer success or solutions engineering.
Company Information: Arda (the platform provider), not the end customer. Charlie’s account has access to many customer tenants and can switch between them to perform their work — investigating issues in one tenant, building an integration for another, and verifying a fix in a third, all in a single session.
Responsibilities: First-line technical support for customer-reported issues. Investigates printing problems, data discrepancies, and workflow failures by inspecting API responses and system logs. Builds Coda-based dashboards and troubleshooting tools that call Arda’s API. Creates and maintains custom integrations for customers with specialized requirements. Escalates platform bugs to engineering with reproducible evidence.
Career Path: Started in customer success or technical support at a SaaS company, developed API literacy through hands-on troubleshooting, and moved into a hybrid support/solutions role. Comfortable with REST APIs, JSON payloads, and browser developer tools but does not write production backend code.

Professional Goals:
- Resolve customer issues quickly and independently without requiring engineering escalation.
- Build self-service tools (Coda dashboards, API scripts) that reduce recurring support tickets.
- Maintain deep product knowledge so support conversations are efficient and accurate.
Motivations:
- Customer satisfaction and trust — a fast, accurate resolution builds the relationship.
- Autonomy — being able to diagnose and fix problems without waiting for engineering.
- Tooling — having API capabilities that expose what the system is doing, not just what it shows the user.

Obstacles:
- Debugging print issues currently requires CloudWatch log access, which is slow and requires AWS expertise.
- No way to see the exact JSON payload sent to Documint without backend log access.
- When a customer reports “my card printed wrong data,” Charlie cannot reproduce the exact print request to compare expected vs. actual output.
- Building Coda integrations requires stable, well-documented API endpoints with predictable response shapes.
Fears/Objections:
- Accidentally triggering a production print job while investigating a customer issue (need for dry-run/preview capabilities).
- Making changes to customer data while debugging (read-only diagnostic access preferred).

Typical Day/Workflow: Receives a support ticket (email, Slack, or ticketing system). Opens the customer’s tenant in Arda to reproduce the issue. Uses Coda dashboards to query API endpoints and inspect data. For print issues, needs to see what was sent to Documint and what template was used. Communicates resolution to the customer and documents the fix.
Technology Use: Browser-based tools (Arda UI, Coda, Postman/curl), basic command-line comfort, REST API fluency. Does not use IDEs or write Kotlin/TypeScript. Accesses AWS console occasionally for log retrieval but prefers API-based diagnostics.
Information Sources: Internal documentation, API reference docs, Slack channels with engineering, customer-reported screenshots and videos.
Decision-Making Process: Does not make product decisions. Influences feature requests through support ticket patterns and escalation reports.

Personality Traits: Methodical, evidence-driven, patient with customers but impatient with tools that hide information. Prefers structured data (JSON, tables) over narrative explanations.
Communication Preferences: Slack for quick questions, structured tickets for bug reports. Provides detailed reproduction steps and evidence when escalating.