On the night of October 7, 2026, we will change the prompt input limit for the meeting summary instruction template.

Currently, the total prompt limit per template is 10,000 tokens. After the change, the total limit will be 50,000 characters. The unit will also change from tokens to characters. (50,000 characters is roughly equivalent to 25,000 tokens, so the limit will be expanded.)

Schedule

Night of October 7, 2026

Customers affected

Customers using MiiTel Meetings and currently using the summary instruction template

Since this change increases the prompt limit, it will not affect existing template settings or behavior. This change will be applied automatically, so no action is required from you.

Details

The prompt input limit for the summary instruction template will change.

Current:

• Unit: tokens
• Limit (total within one template): 10,000 tokens

From the night of October 7, 2026:

• Unit: characters
• Limit (total within one template): 50,000 characters (roughly equivalent to 25,000 tokens)

If you have any questions, please contact us.

We will change the specifications for the values registered in the "Due date" and "Comments" fields of Task records in the Salesforce activity history integration for MiiTel Phone call history.

Inplementation Schedule

Night of Wednesday, October 14

Affected customers

Customers who set the Salesforce integration destination object to the "Task object" in the Salesforce activity history integration for MiiTel Phone call history

Details

Values  in "Due date"

Before:

• Register the created date of the activity history record
• The Tokyo time zone is applied

After:

• Register the date of the dial start time
• The tenant time zone set at tenant creation is applied

Example:

• When the tenant time zone is Tokyo:
  Register the date of the dial start time in the Tokyo time zone
• When the tenant time zone is Jakarta:
  Register the date of the dial start time in the Jakarta time zone

Values in "Comments"

The registration values below will be changed.

• [DIAL_BEGIN_TIME]: Dial start time
• [CALL_BEGIN_TIME]: Call start time
• [CALL_END_TIME]: Call end time

Before:

• The Tokyo time zone is applied

After:

• The tenant time zone set at tenant creation is applied

Starting in late October 2026, we will enhance our internal processes to ensure secure read and write access to objects in your Salesforce environment.

As a result, the following changes will be applied to the Salesforce integration specifications:

• Change 1  Increased API usage when updating activity history
• Change 2  The incoming phone number recorded in activity history for call forwarding will change
• Change 3  Phone numbers for calls made/received via MiiTel for Zoom Phone will be shown in the “Circuit Name” field in activity history
• Change4  Activity history will now be created for voicemails received via MiiTel for Zoom Phone

Scheduled change date

Changes will be rolled out sequentially starting in late October 2026

(We will provide another notice once the start date is confirmed.)

Impact and details by change

Change 1 Increased API usage when updating activity history

Customers affected:

Customers who meet all of the following conditions:

• Using the Salesforce integration
• In Salesforce activity history integration, selecting the “ToDo object” as the Salesforce integration target object

Details:

The number of API calls will change for the operations shown in bold below.

Before:

• Search (retrieve) Salesforce records: 1 time (1 time regardless of whether contacts are retrieved)
• Create activity history: 1 time
• Update activity history:
  • When voice analysis is completed:
    • If any of the following are configured in Salesforce activity history integration: 1 time (0 times if none are configured)
      • Tags
      • Transcription results (excluding fillers) {SPEECH_RECOGNITION}
      • Transcription results (summary) {SPEECH_RECOGNITION_SUMMARY}
      • In-call comments Comments during the call {COMMENT}
      • Call minutes {SUMMARY_WITH_GPT}
  • When minutes creation is completed:
    • If the following is configured in **Salesforce activity history integration: 1 time**
      • Call minutes {SUMMARY_WITH_GPT}

After:

• Search (retrieve) Salesforce records: 1 time (1 time regardless of whether contacts are retrieved)
• Create activity history: 1 time
• Update activity history:
  • When voice analysis is completed: 2 times
  • When minutes creation is completed: 2 times

Change 2  The incoming phone number recorded in activity history for call forwarding will change

Customers affected:

Customers who meet all of the following conditions:

• Using the Salesforce integration
• In Salesforce activity history integration, selecting the “ToDo object” as the Salesforce integration target object

Details:

In the custom field set for the “Incoming number” item in Salesforce activity history integration, phone numbers will be recorded as follows:

Before:

• Answered call history: The Circuit name is recorded
• Missed call history: The Circuit name is recorded

After:

• Answered call history: The forwarded-to phone number is recorded
• Missed call history: The phone number registered at the top as the Call forwarding is recorded

If you have any questions, please contact us.

This week, we released the following 🎉

MiiTel Phone

• CHANGE Automatic update of MiiTel for Salesforce (Night of September 14)
  With this version update, the following two changes have been made.
  ・The URL of the API that MiiTel for Salesforce calls has changed (domain only)
  　Before: app.miitel.jp
  　After: {Company ID}.miitel.jp, or {Company ID}.{Pod code}.miitel.com
  ・Remote Site Settings must be configured on the Salesforce account used for the Salesforce integration
  For details, please see "Domain change and required setup prior to the automatic upgrade of MiiTel for Salesforce

General

• ANNOUNCEMENT  We are gradually switching to a new domain
  For details, see: [Important] Request for re-confirmation of communication permission settings due to MiiTel service domain change.

If you have any questions, please contact us.

We’re updating the internal mechanism of the Calendar integration feature in MiiTel Meetings and MiiTel RecPod.
Since this update is an internal system change, there will be no changes to the UI or operations.
If the calendar integration is disconnected, please reconfigure the integration.

Schedule

From Wednesday, September 30, 2026 onward (to be rolled out gradually)

Affected customers

Customers using calendar integration

Details

This is only an update to the internal mechanism, and there will be no changes to operating procedures or how the UI looks.
However, for about one month starting September 30, we would appreciate it if you could pay attention to the status of your calendar integration.

If the integration is disconnected, please reconfigure the integration.

We are currently verifying our services for compatibility with macOS 27 Golden Gate and iOS 27, which are scheduled for release in September 2026.

Once verification is complete, we will announce the supported OS versions again.

Until macOS 27 Golden Gate and iOS 27 are supported, MiiTel may not work correctly, so please refrain from updating.

Please note that iOS 27 will be supported starting with the next release version.

Affected customers

• Users who use MiiTel on Mac
• Users who use MiiTel Phone Mobile for iOS
• Users who use MiiTel RecPod for iOS

Supported version for iOS 27

It will be supported starting with the next release version (scheduled for an October release).

We apologize for any inconvenience and appreciate your understanding.

If you have any questions, please contact Support.

As previously announced, on the night of September 14, 2026, we automatically upgraded the version of How to set up MiiTel for Salesforce to 1.9.

This version upgrade includes the following two changes:

• The URL of the API that MiiTel for Salesforce calls has changed (domain only).
  Before: app.miitel.jp
  After: {Company ID}.miitel.jp, or {Company ID}.{Pod code}.miitel.com
• You are now required to configure Remote Site Settings in the Salesforce account used for the Salesforce integration.

For details, please see “September 14, 2026: Due to an automatic version upgrade of MiiTel for Salesforce, the domain will change and prior configuration will be required".

If you have any questions, please contact us.

The following updates were released this week. 🎉

MiiTel Meetings/RecPod

• 新機能 Apppend meeting minutes to a Custom Object record (Night of Sep 2)
  You can now append minutes created with the Salesforce-specific template for meeting minutes to a Custom Object record. For details, see “Integrate minutes to Salesforce Opportunity records and Event records ” and “Templates for meeting minutes”.
• 新機能 Amazon S3 integration is now supported for meeting history (Night of Sep 9)
  You can now automatically save recording files from meeting history to Amazon S3. For details, see “Automatically upload meeting recording files to Amazon S3”.

General

• 改善 Added “Last login date/time” to the user list CSV file (night of Sep 9)
  For details, see “We will add “Last login date/time” to the user list CSV file”.
•  お知らせ We are gradually switching to a new domain
  For details, see Important: Please recheck your communication permission settings due to the MiiTel service domain change.

If you have any questions, please contact us.

The following updates were released this week. 🎉

MiiTel Phone

• IMPROVEMENT  Call history CSV exports now include Summaries (Night of September 2)
  When downloading a call history list CSV file from the Call history list or Storage, you can now download the minutes together. For details, please see “Download the call history list in CSV format” and “Download the call history CSV from Storage.

MiiTel Meetings/RecPod

• NEW FEATURE Generate Summaries using templates in Realtime Talk Assist (Night of September 2)
  You can now generate meeting summaries during a meeting using templates you create in advance. For details, please see “Create templates for summary generation” and “Create summaries during or after a meeting (Realtime talk assist)”.

MiiTel Call Center

• NEW FEATURE Set custom view User lists by User group (Night of September 3)
  When creating a Custom view in the Real-time monitor, you can now choose which users to show in the user list by User Group.

General

• ANNOUNCEMENT  We are gradually switching to a new domain
  For details, see Important: Please recheck your communication permission settings due to the MiiTel service domain change.

If you have any questions, please contact us.

From late September 2026, advanced tag registration settings will be available on MiiTel Phone Mobile for iOS. This change applies to MiiTel Phone Mobile for iOS v.3.1.17 and later.

This same change has already been applied to MiiTel Phone Mobile for Android v3.1.16 and later. For details, please see "Early August 2026: Advanced tag registration settings will be available on MiiTel Phone Mobile".

Applicable versions

• v3.1.17 and later

Release timing for the applicable versions

• Version 3.1.17 is scheduled for release in late September 2026. We will provide another update on the release day.

Settings that will be available on MiiTel Phone Mobile

The following settings under Tags in MiiTel Admin > Tag settings (call) > MiiTel Phone settings tab (for details, see Settings for adding a tag)

• Tag items to register
• User settings

Affected customers (impact of the update)

If you use any of the following settings, the tag registration operation will change after updating to version 3.1.17.

• In Tag items to register, Not register parent items that have child items is selected
• In User settings, there are users with Required or Not used selected

Location of settings: Tags in MiiTel Admin > Tag settings (call) > MiiTel Phone settings tab

Details

After upgrading MiiTel Phone Mobile for iOS to version 3.1.17, the change will be applied immediately, and tag registration will behave as follows.

• If Not register parent items that have child items is enabled in Tag items to register
  • Current: Parent items can be registered
  • From v3.1.17: Parent items cannot be registered
• If Required is enabled in User settings
  • Current: Tag settings are optional
  • From v3.1.17: Entering tags will be required
• If Not used is enabled in User settings
  • Current: Tag settings are optional
  • From v3.1.17: Tags cannot be registered. (The tag registration screen will not be displayed.)

If you have any questions, please contact us.