Thena vs Helpshift: Architecture, TCO & Migration Guide

Thena vs Helpshift: Architecture, TCO & Migration Guide

Teams evaluating Thena and Helpshift side-by-side are usually at an architectural crossroads, not comparing two flavors of the same product. These platforms share almost no overlap in ideal customer profile, data model, or pricing structure.

They end up on the same shortlist when a company is changing its support motion. A B2B SaaS company that historically relied on Slack Connect launches a consumer mobile app and needs in-app SDK support. A mobile gaming studio launches a B2B SDK product and needs a dedicated channel for enterprise clients. When these worlds collide, engineering and support operations leaders must decide whether to run dual systems or force one platform to handle a workload it was never designed for.

This guide covers the real technical differences: architecture, data models, pricing math, API constraints, compliance posture, data residency, and the migration path in both directions — including rollback strategy and validation.

Who Each Platform Is Built For

Thena is an AI-native B2B customer support platform designed around Slack and Microsoft Teams as primary support channels. It unifies customer conversations from disparate channels — Slack, MS Teams, Discord, email, and live chat — into a single, intelligent workspace. Known for its native and highly-sophisticated Slack integration, Thena allows teams to build entire support workflows directly within the platform their customers already use.

• Primary buyer: B2B SaaS companies running Slack Connect or Teams channels with enterprise customers
• Core motion: Account-centric — tickets, conversations, and SLAs are organized by customer account
• Clients: Vercel, Amplitude, FOX, Etsy, and others

Helpshift is a mobile-first customer service platform purpose-built for in-app experiences. It delivers a tremendous in-app help experience for many of the world's top mobile apps and mobile games, having pioneered in-app messaging for support that works like modern mobile messaging apps, ensuring users never leave the app.

• Primary buyer: Mobile app developers, gaming studios, consumer-facing companies with high-volume mobile support
• Core motion: Issue-based — support is triggered inside the app via SDK, with device context captured automatically
• Scale: Helpshift utilizes an elastic infrastructure to automatically increase capacity based on demand, supporting one billion devices and 80 million conversations per year.

Architecture: Slack-Native vs SDK-Native

The most significant difference between these platforms is their system of engagement. Thena treats third-party messaging apps as the primary UI. Helpshift embeds the UI directly into your proprietary application.

Thena: Conversation-First, Account-Aware

Thena is built as a workflow engine on top of messaging platforms. With 150+ APIs and core concepts like Organization, Account, Contact, Ticket, Team, and Group, Thena is engineered from the ground up to be modular, scalable, and deeply customizable.

• Channel-first: Slack, MS Teams, Discord, email, web chat, and web forms are all first-class input channels. Tickets can be created from Slack via AI detection, emoji reactions, mentions, shortcuts, and /ticket.
• AI-native architecture: Thena's AI layer performs autonomous detection, classification, and routing — these are not add-on features but core pipeline stages. AI Copilots and AI agents can perform half of the support work by autonomously detecting, tagging, and routing tickets from various channels. This contrasts with "AI-enhanced" helpdesks where AI is a bolt-on layer over a traditional ticket queue.
• State management: Thena listens to messaging channels via bot integrations and uses AI to distinguish casual comments from support requests. When a request is identified, it creates a stateful ticket linked to the chat thread.
• Identity resolution: User identity is tied to the Slack or Teams ID. The organization is mapped via the Slack Workspace ID.
• SLA enforcement: SLAs apply to tickets regardless of channel origin. The system automatically starts SLA timers when an issue is detected, tracks progress toward first response and resolution, and alerts the team when a deadline is at risk.
• Webhook events: Thena webhooks deliver real-time platform events (ticket created, ticket updated, status changed, new message, SLA breach) with a 256KB payload limit and truncation markers for oversized content. Idempotency keys are required — the docs explicitly warn against processing the same event twice.
• MCP server: Thena integrates with external data sources (e.g., CRMs, Zoom), productivity platforms, and offers plug-in support via its MCP for tools like Raycast and Claude.
• Data model: Organization → Account → Contact → Ticket → Messages

Two technical details most buyers miss:

1. Private Slack channels are not auto-discoverable. Thena's docs confirm private channels must be manually added because Slack API limits prevent automatic access or auto-join.
2. Cross-team moves create a new ticket. When a ticket is moved between teams, Thena archives the original, creates a new ticket in the destination team, and links the records. This matters for analytics, audit trails, and any migration that assumes one immutable ticket ID.

Helpshift: Issue-First, SDK-Heavy

Helpshift is fundamentally SDK-driven. Helpshift installs via platform-specific SDKs that embed support and messaging directly into mobile and PC game clients. The SDK routes player issues, logs device context, and allows players to submit tickets or start chat sessions without leaving the game client.

• SDK-first: Helpshift has SDKs for native iOS, Android, macOS, Xamarin, Cocos2d-x, and can also be included in web pages and desktop applications. Unity and Unreal Engine plugins are also available.
• Bot automation: Using bots, Helpshift can automate up to 90% of user issues, improving response times while reducing costs. All of this is delivered out-of-the-box via a simple, lightweight, and easy to integrate SDK.
• Device telemetry: Collected telemetry and conversation context are visible to support agents to speed resolution. Automation and AI are applied at multiple points in the workflow, including automated ticket categorization, AI-first deflection with in-app bots, and proactive engagement triggers.
• State management: The SDK maintains a persistent connection to Helpshift's backend. A user can close the app, return later, and the thread is exactly where they left it, updated via push notifications.
• Identity resolution: Identity is tied to a Device ID or a custom User ID passed from your application's backend during SDK initialization.
• SDK update lifecycle: Because the SDK is compiled into your application binary, any changes to Helpshift integration require an App Store or Google Play release. Current App Store review times average 24–48 hours for routine submissions; emergency hotfixes still go through this cycle unless Helpshift's remote configuration options cover the specific change. Helpshift does support some runtime configuration changes (e.g., toggling bot flows, updating FAQ content) without a binary release, but SDK version upgrades always require a full deployment.
• Language support: Helpshift can provide localized support and automation in over 180 languages.
• Data model: App → User Profile → Issue → Messages (with Custom Issue Fields)

Helpshift's workflow data model is opinionated about metadata. Metadata is read-only and comes from the SDK/device side. Custom Issue Fields (CIFs) are the action-driving layer used to categorize, queue, assign, and route issues. Current docs cap you at 250 active and archived CIFs and 1,000 dropdown options per dropdown CIF. Single-line text CIFs are capped at 255 characters, multiline at 100,000 characters.

Data Model Comparison

Understanding these differences is non-negotiable before planning any migration.

The fundamental distinction: Thena organizes everything around which company raised the issue. Helpshift organizes everything around which device/user raised the issue. This drives every transformation decision during migration.

Pricing and TCO: Per-Seat vs Per-Issue

Thena and Helpshift use fundamentally different pricing models, which makes direct cost comparison dependent entirely on your support volume profile.

Thena Pricing

Thena offers a Starter tier at $29/user/month, but the 1,000 ticket monthly cap can push growing teams toward Standard as request volume increases. The move from Starter at $29/user/month to Standard at $79/user/month represents a meaningful cost increase for scaling internal support operations.

No monthly-only billing option — annual billing required. Microsoft Teams integration is locked behind the Enterprise tier at $119/user/month.

Concrete cost examples:

• 10 agents at Standard: $9,480/year
• 10 agents at Enterprise (required for Teams): $14,280/year — a $4,800/year premium for the Teams channel alone
• Adding Teams to a 25-agent Standard team requires an Enterprise upgrade: $35,700/year vs. $23,700/year, a 51% cost increase

Predictability: High. Your costs scale linearly with internal headcount or the number of enterprise customers you support. The hidden cost is Slack itself — you need Slack Enterprise Grid or paid Slack plans to utilize Slack Connect effectively at scale.

Helpshift Pricing

Helpshift no longer publishes a simple per-seat plan grid on its main pricing page. Its official pricing inputs are interaction volume, solutions activated (Support, Engagement, Trust & Safety, Community), capabilities used (technology, AI, human services), and geography/language coverage. TCO discussions expand quickly beyond software licenses into BPO, moderation, LiveOps, and multilingual operations.

Helpshift does things differently than most software tools. Instead of the usual per-agent, per-month fee, they use what they call an "issue-based" pricing model.

How bot deflection affects billing: Helpshift's pricing incentivizes deflection because issues resolved entirely by bot automation typically count as lower-cost interactions than those that escalate to a human agent. The precise billing boundary — whether a bot-handled issue that the user abandons mid-flow counts as a full or partial interaction — requires direct contract review. However, the structural incentive is clear: at high volume (1M+ issues/year), achieving a 60–70% bot deflection rate (within Helpshift's stated 90% theoretical maximum) can meaningfully reduce per-issue costs compared to full human-agent handling. Model this explicitly before signing.

For reference, Zynga reports a 2x agent productivity increase and 185% more contacts handled after shifting to Helpshift's in-app model (vendor case study — treat as directional, not a guaranteed outcome).

Predictability: Low to Medium. A bug in your mobile app can cause a ticket spike that directly results in a significant overage bill. Budget for seasonal peaks and viral events separately.

Hidden Cost Traps

Thena:

• Organizations using Teams alongside Slack face about a 51% price premium over Standard, since Enterprise is $119/user/month compared with Standard at $79/user/month.
• API access limitations on lower tiers can force upgrades
• Annual-only billing reduces flexibility
• Webhook app setup is API-driven rather than UI-driven — budget engineering time if your ops team expects point-and-click event subscriptions

Helpshift:

• Helpshift's issue-based pricing can lead to unpredictable costs during traffic spikes, seasonal peaks, or viral events
• New features to keep up with the competitors — most of their new offerings cost additional amounts, which increases expenses
• SDK integration requires developer time (not a SaaS-only setup)
• SDK version upgrades require App Store/Play Store release cycles (24–48 hour average review time)
• Archived issue retrieval beyond 12 months may incur additional charges

Compliance, Security, and Data Residency

On a periodic basis Helpshift undergoes external assessments and audits which help them attest and certify against standard industry frameworks for information security and data privacy such as ISO 27001, SOC 2 (Type 2), HIPAA.

Thena's platform is built to support enterprise-grade compliance and privacy standards. However, Thena's public trust page is less detailed than Helpshift's, and several certifications are not publicly confirmed. Request SOC 2 reports and BAA terms directly from Thena's sales team before committing for any regulated workload.

Data Residency

Thena: Data residency options (US-only, EU, multi-region) are not publicly documented. For organizations subject to GDPR Article 46 or data sovereignty requirements, this is a blocking question. Request written confirmation of data processing locations and standard contractual clauses (SCCs) before signing.

Helpshift: Helpshift supports data processing in multiple regions and publishes sub-processor lists. EU data residency is available for enterprise contracts — confirm specifics with your account team. Helpshift's privacy documentation explicitly addresses GDPR transfer mechanisms.

Bottom line: If data residency is a hard requirement, Helpshift has more published documentation to work with. Thena requires direct vendor engagement to resolve this question.

If your organization requires specific compliance documentation, request SOC 2 reports, DPAs, and sub-processor lists directly from both vendors before signing.

API and Data Portability

Thena API

The Thena API suite is organized into three main sections, each serving a distinct purpose in the Thena ecosystem. All APIs require authentication using an x-api-key header. API keys are tied to individual users and can be generated from Dashboard → Organization Settings → Security and Access.

Rate limits: Standard tier: 60 requests per minute per user, org, and IP. Enterprise tier: Custom limits based on your plan. If you exceed your rate limit, you will receive a 429 Too Many Requests error.

Data export: You can export the entire set of requests from your Thena platform, in two formats: XLSX or JSON. Thena also supports CSV ticket export from the current view and search powered by Typesense-style query/filter syntax:

q=*
query_by=title,description
filter_by=createdAt:>2026-01-01&&statusName:!=closed
sort_by=createdAt:asc

Webhook events: Thena delivers real-time events including ticket.created, ticket.updated, ticket.status_changed, message.created, and sla.breached. Payload limit is 256KB with truncation markers for oversized content. Idempotency keys are required — duplicate event delivery is possible and must be handled by your consumer.

createdAt override: Thena's documented ticket-creation API does not expose a public createdAt override field. Historical timestamp preservation during migration is not natively supported. Workaround: store the original creation timestamp as a custom field on the migrated ticket and maintain a separate mapping table in your data warehouse. Confirm with Thena's API team whether an undocumented override is available for bulk migration use cases.

SLA API export: Thena exposes SLA configuration and current SLA state (breach/at-risk/healthy) via API. Computed SLA metrics (historical breach rates, resolution time distributions) are not directly exported — these exist in the analytics layer and require raw ticket data plus external calculation.

Helpshift API

Helpshift exposes a comprehensive set of REST APIs that can be used to access or modify core Helpshift objects, including Issues (read, write, create), Web Messenger (transactional messaging/chat over REST), FAQs (read, write, create), and FAQ Sections.

Pagination: The Helpshift API supports paging, with page sizes up to 1,000 issues per page based on their GitHub sample code. Helpshift uses cursor-based pagination; if a cursor expires or the connection drops during a large historical pull, you must handle retries gracefully.

Rate limits: Helpshift typically enforces approximately 300 requests per minute, but this is not a published self-serve figure — it varies by contract and is negotiable through your Account Manager. Plan for rate-limit coordination before starting any large extraction.

Bulk APIs: The User Hub Bulk APIs can be used to import your end users' data into Helpshift, and export current end user data from Helpshift.

Export paths: You can export Issue data (including Issue body text) by configuring the Get Issue API. Helpshift also provides official Python and Java sample scripts on GitHub for exporting issues to CSV.

Archived data caveat: Helpshift's standard API access covers issue data from the preceding 12 months. After that, data is archived. Archived issues (typically 1+ years old, in resolved or rejected state) may incur retrieval charges beyond the first no-cost request. Pull your history early in the project.

SLA export: Helpshift exposes SLA configuration and current issue SLA state via API. Historical SLA performance metrics are available in the analytics/reporting module but are not directly exportable as raw computed values — you reconstruct them from raw issue timestamps.

Migration Path: Thena ↔ Helpshift

No native migration tool exists between these platforms. Every production migration requires a custom ETL pipeline.

Many teams migrating between Thena and Helpshift do not attempt a 1:1 migration of open tickets. The identity models are fundamentally misaligned — you are mapping Slack IDs to Mobile Device IDs, a connection that rarely exists in either platform's database without a third-party data warehouse bridging the gap. Some teams archive historical data into a warehouse (Snowflake, BigQuery) and start fresh, migrating only knowledge base articles and user profiles.

If you must migrate ticket data, here is what you will face.

The Identity Mapping Problem

This is the primary failure point.

• Thena → Helpshift: You have a Slack User ID and an email. Helpshift requires an app-specific User ID or an email. You must match on email. If the B2B user uses a different email in Slack than in your mobile app, the thread will orphan.
• Helpshift → Thena: You have a mobile Device ID and potentially an email. Thena expects a Slack user. If the consumer user is not in your Slack Connect channels, you cannot natively assign the ticket to them in Thena. You must create a placeholder contact or rely on an email fallback.

Expected identity match rate: In practice, cross-platform email match rates between Slack workspaces and mobile app user databases average 40–70%, depending on whether your product requires account registration with a work email. Plan for 30–60% of historical issues to require manual review or orphaning to a catch-all account.

Thena → Helpshift

This path is uncommon but happens when a B2B SaaS company pivots to a mobile-first product.

Extract from Thena:

curl -X GET "https://platform.thena.ai/v1/tickets?page=1&limit=100" \
  -H "x-api-key: YOUR_API_KEY"

At 60 requests/minute on Standard tier, extracting 10,000 tickets takes approximately 17 minutes (100 per page). Plan for rate-limit handling with exponential backoff on 429 responses.

Transform the data model:

Load into Helpshift:

Use the Helpshift Create Issue API. There is currently no limit on the amount allowable by the Create Issue API, but coordinate RPM estimates with your Helpshift Account Manager for cost projection since every created issue counts toward your billing — including test issues created during migration validation.

Helpshift → Thena

More common — mobile companies expanding into B2B and wanting Slack-native support for enterprise customers.

Extract from Helpshift:

curl -X GET "https://api.helpshift.com/v1/{domain}/issues?page-size=1000&sort-by=creation-time&page=1" \
  -H "Authorization: Basic {base64_encoded_api_key}"

Helpshift uses Basic Auth for REST API access. Page through all results using the total-pages header. For user data, use the Bulk APIs.

// Example Helpshift Issue Payload Snippet
{
  "id": "123456789",
  "title": "App crashing on launch",
  "state": "resolved",
  "custom_fields": {
    "app_version": "2.4.1",
    "os_version": "iOS 17.2"
  },
  "author": {
    "name": "Jane Doe",
    "emails": ["jane@example.com"]
  }
}

Transform the data model:

Load into Thena:

Use the Thena Platform API to create tickets, contacts, and accounts. At 60 req/min on Standard tier, a 50,000-issue migration takes approximately 14 hours of continuous API calls. Enterprise tier customers should negotiate higher rate limits before starting.

Migration Validation Checklist

Before cutting over, verify these metrics against your source system:

Rollback Strategy

Because neither platform has a native undo for bulk imports, rollback requires advance preparation:

1. Pre-migration snapshot: Export your full source dataset (tickets, contacts, attachments, custom fields) before beginning the migration. Store in a versioned archive (S3, GCS) with checksums.
2. Parallel run period: Run both systems simultaneously for 5–10 business days. New tickets are created in the destination; historical tickets remain queryable in the source.
3. Rollback trigger criteria: Define in advance what constitutes a failed migration — e.g., identity match rate below 40%, attachment failure rate above 5%, or critical open tickets not transferred.
4. Rollback execution: Revert DNS/routing to the source platform. If test issues were created in Helpshift, coordinate with your Account Manager on billing reversal for migration-generated test volume.
5. Hard cutover: Only decommission the source system after a full parallel run with zero rollback triggers.

Decision Framework

Is your core product a mobile app or game?
├── YES → Do you need in-app SDK support with device context?
│   ├── YES → Helpshift
│   └── NO → Consider Zendesk or Intercom
├── NO → Is your primary support channel Slack or MS Teams?
│   ├── YES → Thena
│   └── NO → Is your support primarily email/web?
│       ├── YES → Consider Zendesk, Help Scout, or Front
│       └── NO → Evaluate both against your specific channel mix

Choose Thena when:

• Your customers are B2B accounts that expect Slack Connect or Teams support
• You need account-centric SLA tracking and reporting
• AI-driven ticket detection from unstructured Slack conversations is a priority
• Your team already lives in Slack and wants to minimize context-switching
• You need tight Jira/Linear integration directly from chat threads
• Agent headcount is the primary cost driver (≤500 agents)

Choose Helpshift when:

• Your core product is a mobile app or game with SDK-level support needs
• You need device metadata (OS version, app version, device model) attached to every ticket automatically
• Bot-driven deflection at consumer scale (thousands of issues/day) is a requirement
• You need support in 180+ languages out of the box
• Issue volume rather than agent headcount drives your support cost model
• HIPAA, ISO 27001, or COPPA compliance documentation is required and must be independently verified

Choose neither when:

• You need a general-purpose helpdesk for email and web (look at Zendesk, Freshdesk, Help Scout)
• You need deep e-commerce integrations (look at Gorgias)
• You need an open-source, self-hosted solution (look at Zammad)
• Data residency in a specific geography is non-negotiable and neither vendor confirms it in writing

For more on how these platforms compare against other options, see our Zammad vs Helpshift guide and Top Thena Alternatives breakdown.

Key Technical Findings

A summary of non-obvious technical details from this analysis:

1. Data model translation is the hardest part, not the API calls. Mapping Helpshift's device-centric model to Thena's account-centric model (or vice versa) requires decisions about what to preserve, what to restructure, and what to accept as metadata-only. The API mechanics are straightforward; the schema design is not.

2. Rate limits are manageable but require advance planning. Thena's 60 req/min on Standard is tight for large datasets (50K tickets = ~14 hours extraction time). Helpshift's RPM is negotiable but requires Account Manager coordination and is not self-serve. Budget 1–3 days of extraction time for datasets exceeding 50K issues.

3. Attachment migration is the most common failure point. Source URLs expire, file types may not match target constraints, and size limits differ. Every attachment requires download, checksum validation, and re-upload. Do not pass URL strings between platforms.

4. Historical analytics are not portable. Neither platform exports computed metrics (CSAT trends, resolution time distributions, agent performance scores). You get raw data. Build a data warehouse layer (Snowflake, BigQuery, Redshift) before decommissioning the source if historical reporting matters.

5. Archived Helpshift data has retrieval costs. Standard API access covers the preceding 12 months. Issues older than 12 months are archived and may incur charges beyond the first no-cost retrieval request. Pull full history in the first week of the migration project.

6. Compliance verification requires vendor engagement for Thena. Helpshift publishes third-party audit results. Thena's compliance posture requires direct vendor confirmation for SOC 2, HIPAA, and data residency questions. Do not assume parity based on Thena's marketing language.

7. Helpshift test issues cost money. Every issue created via the Create Issue API — including those created during migration testing — counts toward billing. Validate in a sandbox environment if Helpshift provides one; otherwise, budget for test issue volume in your migration cost estimate.

For detailed export mechanics, see How to Export Data from Thena and How to Export Data from Helpshift.

Making the Call

Thena and Helpshift are both strong platforms in their respective domains. The deciding factor is almost always your primary customer interaction surface: Slack/Teams channel or mobile app screen.

Thena is the right tool if you are running B2B support across Slack and Teams and need AI-native ticket detection with account-level visibility. Helpshift is the right tool if your support happens inside a mobile app and you need SDK-level device context, bot automation at consumer scale, and pricing that scales with volume rather than headcount.

The compliance gap is the most underweighted factor in most evaluations: Helpshift has independently verified SOC 2 Type II, ISO 27001, HIPAA, and COPPA certifications with published audit cadence. Thena's compliance posture requires direct vendor engagement to confirm. For regulated industries, this asymmetry can be the deciding factor before any feature comparison is necessary.