The following updates were released this week. 🎉

MiiTel Phone

• NEW  Option to hide Outgoing calls only from the MiiTel Phone Mobile status list (Night of October 28)
  You can now hide the Outgoing calls only status from the list of statuses configurable in MiiTel Phone Mobile. To learn how to configure this setting, see Hide "Outgoing calls only" from the MiiTel Phone Mobile status list.
  This feature is available in MiiTel Phone Mobile for iOS v.3.1.17 and later, and MiiTel Phone Mobile for Android v.3.1.16 and later.
• CHANGE  Unify the color of tags displayed in Call History and the Call History list (new screen) (Night of October 28)
  For details, see October 28, 2026: Unifying the color of tags displayed in Call History and the Call History list (new screen).

MiiTel Meetings/RecPod

• NEW  Add a setting to keep the Meeting Bot out of meetings with specific keywords in the meeting title (Night of October 28)
  With calendar integration, you can now exclude meetings that you do not want to record based on their titles. For details, see Preventing the Meeting Bot from Joining Meetings with Specific Keywords in Their Titles.

MiiTel Call Center

• NEW  Adding alerts for prolonged Incoming call status (Night of October 29)
  You can now receive an alert when the Incoming call status continues beyond a certain period. You can monitor teams and users whose incoming-call status continues for a long time in real time. Use this feature to reduce abandoned calls and improve the response rate.

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.

As previously announced, on the night of October 28, 2026, Unifying the Tag color to White in Call History and Call History List (New screen).

If you have any questions, please contact us.

When Calendar Integration is enabled, you can configure the meeting bot not to join meetings whose titles contain specific keywords.

This lets you exclude meetings you do not want to record by title in bulk.

For details, see “Preventing the Meeting Bot from Joining Meetings with Specific Keywords in Their Titles”.

If you have any questions, please contact us.

On the night of November 5, 2026, we will renew the EV certificate used for code signing MiiTel Phone Desktop.

As a result, a warning screen (Windows protected your PC) may appear when you install or update MiiTel Phone Desktop on Windows.

Scheduled EV Certificate Update Date

Night of Thursday, November 5, 2026

Affected Customers

• Customers currently using MiiTel Phone Desktop on Windows

When the Warning Screen Appears

The warning screen may appear in the following cases:

• Installing MiiTel Phone Desktop
• Updating MiiTel Phone Desktop

The warning screen will not appear when you start or use MiiTel Phone Desktop if you have already installed it.

Why the Warning Screen Appears

Microsoft Defender SmartScreen is a Windows security feature that determines whether a downloaded app is safe.

Immediately after we update the certificate, SmartScreen has not yet accumulated enough installation history for MiiTel Phone Desktop signed with this new certificate. As a result, a security warning may appear even when there is no problem with the app itself.

As more customers install the app and its usage history increases, this warning will disappear automatically. We have confirmed that the app is safe, and it has been signed by the correct publisher (RevComm Inc.), so you can use it with confidence.

What to Do If the Warning Screen Appears

1. On the warning screen, click More info.
2. Confirm that the publisher is RevComm Inc.
3. Click Run anyway.

We apologize for any inconvenience and appreciate your cooperation.

If you have any questions, please contact us.

Urgent Maintenance Notice: October 26, 2026, 0:00 –1:00 AM (JST)

We will perform maintenance on the MiiTel system on October 26, 2026, to provide stable MiiTel services.

As a result of this work, there are expected to be two periods during which the services may be temporarily unavailable. Each is expected to last no more than one minute.

We apologize for any inconvenience this may cause.

Maintenance Schedule

• Japan Standard Time (JST) October 26, 2026 (Mon), 0:00 AM–1:00 AM
• Western Indonesian Time (WIB) October 25, 2026 (Sun), 10:00 PM–11:00 PM

Affected Services and Features

• All MiiTel services
• MiiTel Phone
• MiiTel Admin

Affected Users

• All users currently using the services above

Impact

The following impacts are expected to occur twice during the maintenance window. Each is expected to last no more than one minute.

If an error occurs, wait a moment before logging in or trying the operation again.

All MiiTel services

• New logins may fail.

The following updates were released this week. 🎉

MiiTel Phone

• NEW Released MiiTel Phone Mobile for iOS v.3.1.17 (October 21)
  For details, see MiiTel Phone Mobile for iOS v.3.1.17 released.
• NEW Added “Incoming” to the MiiTel Phone status (Night of October 21)
  We re-released the feature that was temporarily suspended, which sets the status to Incoming when MiiTel Phone receives a call. For details, see Re-releasing the feature that sets the MiiTel Phone status to Incoming when receiving a call.

MiiTel Call Center

• NEW Added "Incoming calls" to User list reports and Summary (Night of October 21)
  We re-released the feature that was temporarily suspended and adds Incoming calls to the user list report. For details, see Re-releasing the feature that sets the MiiTel Phone status to Incoming when receiving a call.

General

• Announcement We are gradually migrating to a new domain
  For details, see [Important] Please reconfirm your communication allowance settings and more due to the MiiTel service domain change.

If you have any questions, please contact us.

We investigated the impact of the PHP vulnerability (PHP2Shell / CVE-2026-109618, CVE-2026-109619), reported on October 21, 2026. As a result, we confirmed that MiiTel services are NOT affected.

Here are the details.

1. Impact on MiiTel Services

MiiTel services are not affected by this vulnerability as they do not use PHP.

2. Impact on Third-Party Services

Based on information available at this time, we have found NO impact on any third-party services used internally by MiiTel.

3. About the Third party  Integration Services

For third-party services integrated with MiiTel (such as Salesforce or kintone), please check the updates directly from each service provider.

Based on public updates from major integration providers (such as Salesforce, HubSpot, kintone, and Amazon S3), no service outages, maintenance, or other impacts related to this vulnerability have been reported at this time.

4. Impact on Our Product Information and Corporate Websites

The product information website (miitel.com) and the corporate website (revcomm.com) use WordPress and PHP.

We have confirmed that our hosting provider applied a patch for this vulnerability on October 22.

If we learn of any new information, we will provide updates  in this announcement or through a separate notice.

If you have any questions, please contact us.

As previously announced, on the night of October 15, 2026, We changed 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.

For details, please see “Change in specification for 'Due Date' and 'Comments' in Task record of Salesforce Activity History Integration for MiiTel Phone call history".

If you have any questions, please contact us.

The following updates were released this week. 🎉

MiiTel Phone

• CHANGE Increased the prompt limit for summary templates in call history (Night of October 15)
  For details, see October 15, 2026: Change the prompt input limit for the meeting summary instruction template to 50,000 characters.
• CHANGE Changes to 'Due Date' and 'Comments' field values in Tasks for Salesforce activity history integration in MiiTel Phone Call history (Night of October 15)
  For details, see Change in specification for 'Due Date' and 'Comments' in Task record of Salesforce Activity History Integration for MiiTel Phone call history.

MiiTel Meetings/RecPod

• CHANGE Increased the prompt limit for summary templates in meeting history (Night of October 15)
  For details, see October 15, 2026: Change the prompt input limit for the meeting summary instruction template to 50,000 characters.
• NEW  Option to disable Meeting recording generation now available (Night of October 15)
  You can now configure the setting so that recording data is not generated even when the meeting bot joins the room. (By default, recording data is generated.)
• NEW  Meeting history access restriction can now be set from the Realtime talk assist screen as well (Night of October 15)
  For details, see Restrict access to meeting history.

MiiTel Call Center

• NEW  Aggregation conditions for “Missed incoming calls” shown in the Real-time monitor can now be customized (Night of October 15)
  We added “Item definitions” to the display rules in the MiiTel Call Center settings. This allows you to customize the definition of the aggregation conditions for missed incoming calls. For details, see Realtime monitor - Customize the definition of missed incoming calls.

MiiTel Synapse (Copilot)

• NEW  You can now expand the width of the chat area in Copilot Plus (Night of October 14)
  For details, see You Can Now Expand the Width of the Copilot Plus Chat Area.

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 support.

We would like to correct an error in the description for CHANGE  2 in the previously announced “Upcoming changes to Salesforce integration specification (Starting late October 2026).”

Correction details

There was an error in the “Before” description for “ CHANGE 2 The incoming phone number recorded in activity history for call forwarding will change”

Correct:

Before:

• Answered call history: The automatic call forwarding source number is recorded
• Missed call history: The automatic call forwarding source number is recorded

Incorrect:

Before:

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

If you have any questions, please contact us.