What changed in EosHQ

Campaign management joins EosHQ CRM

New

• Campaigns and Campaign Members. Sales and marketing teams can plan Campaigns, organize participating Leads and Contacts, track member responses, associate originating Leads and influenced Opportunities, and connect sales Activities to a Campaign.
• Campaign reporting. Supplied reports cover Campaign performance, Campaign Member status, and Campaign-influenced Opportunities.
• Campaign-aware Agents. New Skills let authorized users and Agents create Campaigns and Campaign Members, while published Agents can run in Campaign and Campaign Member record context.

Improved

• Sales dashboard. The dashboard now shows active Campaigns and Campaign status alongside pipeline, Leads, and upcoming Activities.

International work, configurable operations, and safer execution

New

• Seven-language product experience. EosHQ now supports English, German, Hindi, Italian, Korean, Portuguese, and Spanish across application labels and transactional email, helping distributed teams work in a familiar interface.
• Companies and Contacts workspace. Teams can manage customer organizations and people in a dedicated, metadata-aware workspace instead of treating them as generic records.
• Configurable CRM. Sales teams can manage Leads, Opportunities, Activities, Companies, and Contacts; review pipeline and follow-up from a Sales dashboard; and run published Agents from CRM records. Administrators can configure Opportunity stages, hierarchical Territories, role-based CRM access, layouts, fields, Skills, Agents, and reports for their organization.
• Reusable operations packages. Administrators can install governed object, field, view, and Agent definitions for an industry or operating model, making structured rollout faster.
• Credential and qualification controls. Teams can model qualifications, check work eligibility, and monitor expiring credentials before assignment decisions create delivery risk.

Improved

• List views and filters. Metadata-driven columns, reusable filters, and clearer cell rendering make larger operational datasets easier to scan and act on.
• Project cloning. Repeatable project structures can be copied with their operational relationships, reducing setup work for similar engagements.
• Agent simulation safeguards. Simulated runs have stronger boundaries around live effects, giving reviewers better confidence before activation.

Fixed

• Tenant and access isolation. Access checks, navigation visibility, and organization-specific state were tightened across key screens so users see the records and actions intended for their role.
• Project, Files, Approvals, Marketplace, and billing page loading. Several permission and route failures were corrected, reducing blank states and interrupted navigation.

Better conversations and resource decisions

New

• Resource-analysis Agent skills. EosHQ can assess capacity, over-allocation, under-utilization, and staffing trade-offs, helping managers make decisions with operating evidence.
• Expanded ticket-resolution tools. Agents gained more structured ways to classify, assign, update, summarize, and respond to tickets.

Improved

• Conversation context across channels. EosHQ Chat and supported messaging channels preserve clearer context and present more structured answers, reducing repeated explanation.
• Project task relationships. Dependencies now stay under their project context, improving schedule interpretation and sample-data fidelity.

Fixed

• Voice and chat execution. Corrections to message handling and skill compilation improved reliability when people ask EosHQ to take multi-step actions.
• Website navigation. Menu behavior was repaired across page layouts, making product and resource pages easier to reach.

More reliable projects, time, outreach, and connected chat

New

• Chat-platform access to EosHQ. Conversation support expanded across workplace messaging channels so teams can ask questions and start approved work where they already coordinate.
• Marketing and outreach workflows. Structured campaign and follow-up capabilities help teams move from target lists to reviewable communication.

Improved

• Project and time-entry workflows. Editing, validation, and project-linked time behavior were refined to reduce correction work before billing.
• Agent field grounding. Skill execution uses stronger schema guidance, reducing invented or unsupported fields in Agent actions.

Fixed

• Project page stability. Multiple project navigation, loading, and editor defects were corrected.
• Outreach automation reliability. Queueing and campaign-processing fixes reduced stalled or misrouted follow-up work.

Files, stronger help, and platform reliability

New

• Files workspace. Users can publish, browse, and retrieve organization and project files from a dedicated EosHQ experience.
• Agent file publishing. Governed skills can create and publish useful file outputs, supporting document-heavy operational work.

Improved

• Help and reference search. Updated indexes and routing make it easier to find product guidance and Agent skill references from the app.
• Application runtime modernization. The server runtime moved to a current supported generation, improving the platform’s maintainability and release foundation.

Fixed

• Project screen behavior. Project data, layout, and interaction fixes improved day-to-day delivery management.
• File access and download paths. Storage and API rules were aligned so authorized users can retrieve the files their work depends on.

Recovered release continuity and consolidated product improvements

Improved

• Project operating experience. A broad set of project, task, ticket, billing, time, settings, and user-management changes was consolidated into the main release line, giving teams a more consistent cross-module experience.

Fixed

• Release continuity. Application work from parallel development lines was recovered and reconciled, preserving customer-facing improvements that otherwise risked being left out of subsequent releases.

Cleaner time and task operations

Improved

• Time-entry experience. Time views, editing, worked-time calculations, and project associations were refined, helping users record time with fewer corrections.
• Task and ticket handling. Assignment and status behavior was tightened across list, board, project, and ticket views.

Fixed

• Project rollups and hourly values. Corrections to background calculations improved the consistency of project totals and labor-value reporting.

Foundations for dependable billing and assistant-driven work

New

• Hierarchical hourly rates. EosHQ can resolve labor rates across assignment, task, project, and member levels, giving services teams a more practical basis for project cost and billing calculations.
• Assisted data and process setup. The setup experience gained additional server-backed guidance and access-state checks, helping organizations establish working configuration more safely.

Improved

• Project financial rollups. Time and assignment changes now feed more complete project-level calculations.

Fixed

• Projects with no tasks. Empty-project handling was corrected so a valid project can load and be configured before tasks exist.