The scheduled maintenance originally planned for October 6, 2025 (Mon) , is rescheduled.
We apologize for any inconvenience this may cause our customers.

Before the change

• Japan Standard Time (JST)
  October 6, 2025, 3:00 AM - 4:30 AM
• Indonesia Time (WIB)
  October 6, 2025, 1:00 AM - 2:30 AM

↓

After the change

• Japan Standard Time (JST)
  October 27, 2025 (Mon) 3:00 AM - 4:30 AM
• Indonesia Time (WIB)
  October 27, 2025 (Mon) 1:00 AM - 2:30 AM

If you have any questions, please contact support.

We have released MiiTel Phone Desktop v3.6.0.

New Features

A confirmation dialog can now be displayed when placing a click-to-call call.

If you have any questions, please contact us.

A confirmation dialog can now be displayed when placing a click-to-call call.
This prevents you from accidentally clicking on the wrong number and calling an unintended number.

Applicable MiiTel Phone products and how to set up

• MiiTel Chrome Extension
• MiiTel Phone Desktop
• MiiTel Phone for Salesforce

*MiiTel Phone for HubSpot and the JavaScript Widget are not supported.

If you have any questions, please contact us.

We have made some updates for MiiTel RecPod 25.09.01.

Updates

• Some improvements are made to the audio uploading process.

September 26 (Fri), 2025: We have changed the maintenance date.

・JST
October 6 (Mon), 2025, 3:00 AM – 4:30 AM (JST)
・WIB
October 6 (Mon), 2025, 1:00 AM – 2:30 AM (WIB)
↓
・JST
October 27 (Mon), 2025, 3:00 AM – 4:30 AM (JST)
・WIB
October 27 (Mon), 2025, 1:00 AM – 2:30 AM (WIB)

To provide a stable MiiTel service, we are currently updating our system configuration.

In accordance with this change, we will be performing maintenance on the MiiTel system on October 27 , 2025 (Mon).

During the maintenance period, the MiiTel services will be unavailable for approximately 60 minutes.

We apologize for any inconvenience this may cause.

1. Maintenance date and time:

• JST
  • October 27 (Mon), 2025, 3:00 AM – 4:30 AM (JST)
• WIB
  • October 27 (Mon), 2025, 1:00 AM – 2:30 AM (WIB)

2. Affected services

• MiiTel Phone
• MiiTel Phone Mobile
• MiiTel Meetings
• MiiTel Admin
• MiiTel Phone Analytics 
• MiiTel Meetings / Recpod Analytics
• MiiTel Call Center
• MiiTel Recpod
• Incoming Webhook

3. Affected customers:

All users of the above services

4. Expected Impact:

MiiTel Phone、MiiTel Phone Mobile

• Unavailable
• If maintenance is started during a call, the call can continue. 

  'Tag', 'comment', and 'related to' cannot be registered after the call ends.

  Please set the tags and comments from the call history in MiiTel Analytics after the maintenance is completed.

MiiTel Admin > Incoming call rule set in the incoming call filter

Actions to call MiiTel Phone or MiiTel Phone Mobile included in the Answering rules sets in the Incoming Call Filter applied during the maintenance period will not work (Call all users in a group or Call specific user).

*The following actions work.

• Play sound 
• Voice mail
• Auto transfer 
• Play sound and receive button input from user (IVR)
• Queue (works, but MiiTel Phone does not call) 
• Send SMS

*If the following answering rule is set, Actions 2 and 3 will work and you will be able to see the Call history after the maintenance is completed.

• Action 1: Call all users in the group 
• Action 2: Play sound 
• Action 3: Voice mail

MiiTel Meetings

• Video bot cannot join a meeting during a meeting (cannot record).
• With the Google Calendar integration and the Microsoft Outlook Calendar integration, you can have the meeting bot join automatically (and record).

*The bot name may be different from the name you set. 

* Recording indicator does not work.

*Zoom meetings using Zoom integration can be recorded.

MiiTel Admin、MiiTel Phone Analytics、MiiTel Meetings / Recpod Analytics

• Unavailable
• If a CSV file is scheduled to be created in storage during the maintenance period, or if the file is being created when the maintenance starts, the CSV file will not be created.

* For CSV files that were not created, please create them from storage after the maintenance is completed.

MiiTel Call Center

• Unavailable

MiiTel Recpod

• Functions other than recording are not available.
• (audio upload is not available, transcription and minutes cannot be checked)
• Recording is available.

Incoming Webhook

• After the maintenance is finished, please resend the request from the sender or upload the file from MiiTel Analytics > Call History or Meeting History.

Note

• After the maintenance is finished, the call and meeting history will be reflected in 
  • MiiTel Analytics > Call History, Call History List 
  • MiiTel Analytics > Meeting History

We will be performing a system maintenance about MiiTel Synapse Copilot on the following date and time.
During the maintenance period, the service will be unavailable for approximately 10 minutes.

We apologize for any inconvenience this may cause.

Maintenance date and time

September 25, 2025 (Thu) 22:00 to 22:30 (JST) / 20:00 to 20:30 (WIB)

Affected services

The following features using MiiTel Synapse Copilot

Individual call history > Ask Copilot
Individual meeting history > Ask Copilot
MiiTel Meetings Analytics > Chat with Copilot

Affected customers

Users currently using MiiTel Synapse Copilot

Impact

During the maintenance period, the feature will be unavailable for approximately 10 minutes.

• If you send a question to MiiTel Synapse Copilot during maintenance, it will result in an error.

If you have any questions, please contact support.

We have completed compatibility testing for iOS 26, and it is now a supported OS for MiiTel Phone Mobile and MiiTel RecPod.
・MiiTel Phone Mobile for iOS v3.1.11 or later
・MiiTel RecPod for iOS version 25.08.11 or later

macOS Tahoe is still undergoing compatibility testing.

We are currently conducting compatibility testing for macOS Tahoe and iOS 26, which are scheduled for release in September 2025.

Once testing is complete, we will announce these as supported operating systems.

• MiiTel
• MiiTel Phone Mobile for iOS
• MiiTel RecPod for iOS

TPlease refrain from updating to macOS Tahoe and iOS 26 as the above systems and apps may not function properly until they are compatible with the OS.

Please note that iOS 26 is supported from the latest version of the app.

Therefore, when using iOS 26, please update the app to the latest version.

Affected customers

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

iOS 26 Compatible Versions (Planned)

• MiiTel Phone Mobile for iOS v3.1.11 or later
• MiiTel RecPod for iOS Version 25.08.11 or later

We apologize for any inconvenience caused to our customers.

Effective October 2, 2025, the previous_id will be changed for multiple transfers in Outgoing Webhook (Call).

Scheduled date of change

October 2, 2025 (Thu) 

Description of Change

When multiple transfers occur during a call, the previous_id for the second and subsequent transfers will be changed.

Before Change:

・The previous_id of transfer calls is the sequence_id of the first answered call.

Example: Incoming Call > Transfer > Transfer

1. Incoming Call (sequence_id: A)
2. Transfer (sequence_id: B, previous_id: A)
3. Transfer (sequence_id: C, previous_id: A)

After Change:

・The previous_id during a transfer is the sequence_id of the previous transfer source call.
(From the second call onwards, the previous_id will be the sequence_id of the previous call, not the initial call.)

Example: Incoming Call > Transfer > Transfer

1. Incoming Call (sequence_id: A)
2. Transfer (sequence_id: B, previous_id: A)
3. Transfer (sequence_id: C, previous_id: B)

We have released MiiTel Phone Mobile for iOS v.3.1.11.

Updates

• Some internal processing has been improved.

Regarding Amazon S3 integration, we will support S3 bucket in regions created after March 20, 2019,
starting October 2, 2025 (Thu).

In conjunction with this change, please add a policy (s3:GetBucketLocation) that allows the retrieval of region information to the permission policy used for Amazon S3 integration.

Currently, customers using regions created before March 19, 2019, can continue to use the integration without adding the policy. However, explicit permission will be required in the future.

We will notify you again when this becomes mandatory.

If you are using the following regions, you can continue to use the integration without adding the policy at this time.

• Asia Pacific (Tokyo)
• Asia Pacific (Osaka)

Support start date

October 2, 2025 (Thu)

Regions where support will begin

Regions created after March 20, 2019
https://docs.aws.amazon.com/global-infrastructure/latest/regions/doc-history.html

Required Policy

{
    "Action":
    "s3:GetBucketLocation",
    "Effect": "Allow",
    "Resource": "arn:s3:::＜bucket name＞"
}

Entire permission policy

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "s3:PutObject",
            "Resource": "arn:aws:s3:::＜bucket name＞/＜folder name＞/*"
        },
        {
            "Effect": "Allow",
            "Action": "s3:ListBucket",
            "Resource": "*"
        },
        {
            "Action": "s3:GetBucketLocation",
            "Effect": "Allow",
            "Resource": "arn:aws:s3:::＜bucket name＞"
        }
    ]
}