Plum IVR Support

Hi, Unfortunately, no, that is not the purpose of the is_pci flag. This flag only determines which pool of systems will be used to execute your application once the call begins. In order to guarantee PCI compliance, you should only send non-PI/PII data to the outbound APIs. The data that is sent to ...

Hi,

Only a designated SMS phone number can use the SMS functionality. One number, unfortunately, cannot be utilized for both SMS and outbound calling with an application.

Please let us know if you have any further questions.

Regards,
Plum Support

Hi, When queuing an outbound call from our Fuse+ platform you have the option to set the phone number of your choice as the ANI (the number the call is coming from). We currently support custom caller ID displays of up to 15 characters (including spaces) for local phone numbers only. This feature is...

Hi,

No problem, glad we could be of help. Let us know if you have any other questions.

Regards,
Plum Support

Hi,

If you go to the Audio Manager, you will see the built-in prompts under the User prompt. You can delete the text in the built-in prompts to mute these prompts.

Regards,
Plum Support

Hi,

The docs have been updated with some additional languages, including French. We are working to get phonemes for all of the supported languages added as soon as possible.

https://www.plumvoice.com/docs/dev/deve ... ts#phoneme

Regards,
Plum Support

Hi, To shorten the waiting time between prompts, you can adjust the speech timeout. We would recommend lowering the incompletetimeout property which will reduce the amount of time the platform waits in determining that the caller has finished speaking. You can find an example here: https://www.plumv...

Hello, After reviewing your code there are a few small changes we would make. For example there is no reason to perform a second <record>, that should be a <field>. There also is no reason to check the session.connection.callee_type after the first <record> is complete. The callee type detection occ...

Hi,

Lexicon is not planned to be utilized in the near future. However, it has been added to our feature list, and you should reach out to your account manager to help it get prioritized into a future release.

Thanks,
Plum Support

Hi, Unfortunately we do not support the <lexicon> tag because it is not fully supported by our Text-to-Speech engines. Your best option for translations is to use the <phoneme> tag around each of the words that need to have their pronunciations altered. However, each engine supports different phonem...

Hello, We ran some analysis on your audio file, and it seems as though the issue is with your block align value. It is showing up as a value of 8 when it should be a value of 1. We recommend re-encoding your audio file using sox to fix this issue. Let us know if you have any issues. Regards, Plum Su...

Hi Graham, Errors are logged automatically in the call logs whenever a <catch> element is triggered. In the code below, <submit> will trigger the <catch> element as the file process_id.php does not exist. The error (error.badfetch) will be logged before user is transferred. Furthermore, the <catch> ...

We've also called into your application we don't find the "waiting time" after input outside the industry standards, or even noticeable. As our sales team suggested, you can ask your users to enter the # sign after input, which is the industry standard for ending DTMF input. A note about your ZIP co...

All API requests authenticate using HTTP Basic Authentication. Use the same email address you use to log into your Fuse account for the username value. Your Developer Key, located in your Account Settings, functions as your password. More details can be found in the docs: https://www.plumvoice.com/d...

Hi,

The base URL for all API requests is https://fuse.plumvoice.com/api.

Please refer to our documentation on Fuse+ APIs here: https://www.plumvoice.com/docs/fuse/apis.

Regards,
Plum Support