Origami Version 6.3.1B: Smarter Omnichannel, Redesigned Calendar & Flexible Date Formats

Version 6.3.1B delivers upgrades across four areas: a smarter Omnichannel that pulls in emails sent from outside the system and supports WhatsApp Coexistence, more flexible PBX management with multi-account support, a fully redesigned calendar for desktop and mobile, and precise control over how dates are displayed – in charts and in fields. Every update follows the same logic: the system works the way you do.

In this article:

• Omnichannel – external emails auto-imported + WhatsApp Coexistence
• PBX – multiple accounts, multiple entities, clearer settings
• Calendar – redesigned for desktop and mobile, meeting reschedule without duplicates, resource tooltips
• Date display – flexible viewing formats for charts and date fields

Here are the key updates in this version:

External Emails in Omnichannel – All Communication in One Place

Emails sent from Gmail or Outlook appear automatically inside the Omnichannel thread

Until now, emails sent directly from a personal inbox (Gmail / Outlook) didn’t appear in Omnichannel – creating gaps in the communication record. Now the system detects emails sent via a connected 365 / Gmail integration and pulls them automatically into the relevant conversation, alongside incoming emails and all other correspondence.

Step by step:

1. A user sends an email to a client directly from their personal inbox (Gmail / Outlook).
2. The system detects the email via the existing 365 / Gmail connection.
3. The email is automatically pulled into Omnichannel and displayed under the relevant record.
4. It appears alongside all other correspondence – incoming, outgoing, from all channels – under the same thread.

Who it’s for:

• Service and sales teams who work from both their personal inbox and the system.
• Organizations using Gmail or Microsoft 365.

What it solves / examples:

• Prevents emails sent outside the system from “disappearing” from the record.
• Centralizes all client communication in one place – with no manual effort.
• Example: a rep sends an email from Outlook to a client – the email automatically appears in Omnichannel under the same thread.

WhatsApp Coexistence – Work from the App and the System in Parallel

Connect an existing WhatsApp Business account – without disconnecting the app

Previously, connecting WhatsApp to Omnichannel required a number that hadn’t been used before – meaning businesses had to start with a new number and lose existing history. Now you can connect an existing WhatsApp Business number – including ones already active in the app – and continue working from both places simultaneously, without interruption.

Step by step:

1. The user opens WhatsApp settings in Origami and starts the Embedded Signup process.
2. The system automatically detects whether the number is already active in the WhatsApp Business app.
3. If yes – the connection is made without disconnecting the app (Coexistence mode).
4. If no – a full registration is completed as usual.
5. After connecting: the user can work from both Origami and the app in parallel. Conversations are visible from the connection point onward.

Who it’s for:

• Businesses managing conversations from both mobile and the system.
• Organizations that want to connect their existing WhatsApp number without starting fresh.

What it solves / examples:

• Enables continuous work between Origami and the WhatsApp app – no disconnection, no lost history.
• Eliminates the need to start with a new number and abandon existing contacts.
• Example: a business managing client conversations from both mobile and the system – continues working in both places without disruption.

Multiple PBX Accounts & Multiple Connected Entities

Full flexibility – every department, line, or provider – managed separately from one screen

Until now, the system supported a single PBX account. Now you can connect multiple telephony accounts and link each one to a different entity and phone field. Incoming calls are identified across all accounts, and for outgoing calls – users choose which account to call from.

Step by step:

1. The user opens PBX settings and adds multiple telephony accounts.
2. For each account, they define which entity and phone field it’s linked to.
3. Incoming call: the system identifies the number across all entities in all accounts and displays the caller’s details.
4. Outgoing call: the user selects which PBX account to call from.

Who it’s for:

• Organizations with more than one telephony provider.
• Service and sales teams working with multiple phone lines or branches.

What it solves / examples:

• Enables managing calls from multiple accounts in one place.
• Example: a company with two PBX providers (different branches) – can identify calls from either and choose which account to call from.

Redesigned Calendar – Desktop & Mobile

Compact header, Bottom Sheets on mobile, a full month in one screen

Origami’s calendar has been comprehensively redesigned. A new unified header lets you manage calendars, view type, and filters from a single dropdown. On mobile – filters and event details open as Bottom Sheets. The result: a full month fits on one screen, navigation is clearer and more intuitive across all devices.

Step by step:

1. The user opens the calendar and sees a new compact, single-line header.
2. Selects calendars and view type from a unified dropdown.
3. On desktop: filters are available as usual. On mobile: filters open as a Bottom Sheet.
4. Clicking a day in the calendar creates a new event.
5. External events are view-only; internal events can be edited or deleted.
6. On mobile: event details open as a Bottom Sheet.

Who it’s for:

• All calendar users in the system.
• Teams managing scheduling, meetings, and resources – on desktop and mobile.

What it solves / examples:

• Better screen space utilization – a full month fits in one view.
• Significantly improved mobile experience with Bottom Sheets and clear navigation.
• A consistent, intuitive interface across all platforms.

Reschedule Meetings via Webform Without Creating Duplicates

Change the time or date – the existing event updates in the external calendar, no duplicate created

Previously, changing a meeting’s time via an edit form created a new event in the external calendar instead of updating the existing one. Now the system updates the existing event directly and syncs the change to Google Calendar (and other connected calendars) – no duplicates, no inconsistencies.

Step by step:

1. The user opens an existing meeting via an edit form.
2. Changes the time or date of the meeting.
3. Saves – the system updates the calendar field in the entity.
4. The existing event in the calendar is updated (no new event is created).
5. The change syncs to the connected external calendar (Google Calendar, etc.).

Who it’s for:

• Users who manage meetings across the system and external calendars.
• Automation workflows that depend on meeting time changes.

What it solves / examples:

• Prevents duplicate events in the external calendar.
• Keeps the entity and external calendar in sync.
• Example: a user moves a meeting from 09:00 to 10:00 – the event updates in Google Calendar instead of creating an additional one.

Tooltip for Long Resource Names in Calendar

Name cut off? Hover to see it in full

In the calendar’s resource filter, long names were truncated and hard to read. Now hovering over any resource in the list shows a tooltip with the full name – without changing the existing layout.

Step by step:

1. The user opens the calendar and expands the resource filter.
2. Hovers over a resource with a long name.
3. A tooltip displays the full resource name.

Who it’s for:

• Teams with long or complex resource names.

What it solves / examples:

• Fixes truncated text in the resource filter – without changing the UI.
• Example: a long resource name is cut off in the display – hovering shows the full name.

Date Display Format for Charts

Control how dates appear on chart axes – daily, weekly, monthly

In Chart, Pie, and Trend widgets – when a date field is used as the series axis – you can now choose a display format tailored to the interval (daily / weekly / monthly). The format affects the display only – the underlying data doesn’t change.

Step by step:

1. The user creates or edits a Chart / Pie / Trend widget.
2. Sets a date field as the series axis and selects an interval (daily / weekly / monthly).
3. A new option appears: “Viewing Format”.
4. The user selects the desired format – dates on the chart update accordingly.

Format options by interval:

• Daily: Day name | Day + month name | Day + month + year | Hebrew date
• Weekly: Week number + month | Week number + month + year | Date range (e.g. 11.2.2024 – 18.2.2024)
• Monthly: Month name | Month name + year

Who it’s for:

• Users working with date-based reports and charts.
• Teams that need visual adaptation for different audiences or languages.

What it solves / examples:

• Improves chart readability – shows only the relevant date detail for the interval.
• Example: a monthly chart can show just the month name, or month + year – depending on the context.

Viewing Format for Date Fields

Control how the date is displayed – without changing the stored value

Date fields now support a separate display format setting. Users enter and edit dates as usual – but after saving, the date is displayed according to the chosen format. The stored value itself doesn’t change.

Step by step:

1. The user opens the settings for a date field.
2. Selects a “Viewing Format” from the available options.
3. When entering a date – the selection process remains unchanged.
4. After saving – the date is displayed according to the chosen format.

Format options:

• Hour | Hour-Day | Day-Month | Day-Month-Year | Month only | Month-Year | Year only | Hebrew Date

Who it’s for:

• Users who want control over how date fields are displayed.
• Teams that need visual adaptation based on context.

What it solves / examples:

• Displays only the relevant information – without affecting the stored data.
• Example: a date of birth field – displays only the year, even though the system stores the full date.

PBX Settings UX Improvements

Clearer field names, logical order, and tooltips – PBX setup without the confusion

The PBX settings screen has been improved: fields are reordered, renamed for clarity, and every field now has a tooltip. The main change: the field previously called “Take Call URL” is now “Outgoing Call Webhook URL” – making its purpose immediately clear.

Step by step:

1. The user opens the PBX settings screen.
2. Sees all required fields in a clear, accessible order.
3. Hovers over the ? icon next to any field – a tooltip explains what it’s for.
4. Fills in the fields and passes the details (Entry call URL, secret key) to their telephony provider.

Who it’s for:

• Users setting up a PBX connection to the system.
• Technical teams and IT staff working with telephony providers.

What it solves / examples:

• Eliminates confusion during PBX setup.
• Makes the integration process with telephony providers easier.
• Example: instead of the unclear “Take Call URL”, the user sees “Outgoing Call Webhook URL” and immediately understands what to fill in.