InQueueVoicemailComponent.js: JSX value should be either an expression or a quoted JSX text (300:12)

That's if I do twilio flex:plugins:start to run locally.
Twilio flex:plugins:deploy just returns failed to compile with no other output

After pressing the "Delete Recording" button in the voicemail task UI, there is no visual confirmation that the recording has been successfully deleted.

When I choose voicemail, call is delivered, when I click on Delete Recordings, nothing happens. When console on, I see the following:

The 404 is expected as this is not the correct URL for this plugin. The console.log of the baseUrl on delivery of the call does show the correct value, but this is using an incorrect baseUrl value. See below for initial render of baseURL:

Hi,

I am trying to create a voicemail with transcriptions enabled. I created a simple studio flow with a Record Voicemail widget that calls the service of the installed plugin. When I inspect the created task, everything seems to work, as it has the TranscriptText attribute:

But in the UI, the transcription text is not displayed (the recording is working though):

I have an assumption - the VoicemailComponent is looking for an attribute transcriptionText, but this actually doesn't exist - the attribute is called TranscriptText. Can this be the problem, or am I missing something?

The code is currently calling evaluateTaskAttributes several times per execution. Refactor the code to optimise the number of calls made to this endpoint

I have the plugin compiled and deployed with the fix noted to a previous issue. Things seem to work fine except Place Outbound call for either Callback or Voicemail. When I click place outbound call I see this:

I do have legacy dialpad enabled. Behavior is same Firefox/Chrome. Is there somewhere else outbound dialing must be enabled?

Hello,

We have been using this plugin for a bit now and have noticed that callers who opt for the callback option are called prior to those that wait in the queue due to the callback task having a higher set priority. Ideally, the caller would retain their spot in line vs jumping to the head of the queue, but you aren't able to programmatically set a queue entered date to tell taskrouter that the task has been in queue for longer than the created date.

This should be edited for this plugin as it creates a negative user experience, do you have any guidance on how to fix this?

I got this error when I run twilio flex:plugins:deploy --major --changelog "Change plugin to use the latest Flex plugin for the Twilio CLI" --description "Queued Callback and Voicemail Plugin"

(node:30265) UnhandledPromiseRejectionWarning: Error: Cannot find module 'craco-config-flex-plugin'
Require stack:

• /Users/pangge/twilio/voicemail/plugin-queued-callbacks-and-voicemail/craco.config.js
• /Users/pangge/.twilio-cli/node_modules/@craco/craco/lib/config.js
• /Users/pangge/.twilio-cli/node_modules/@craco/craco/scripts/build.js
  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
  at Function.Module._load (internal/modules/cjs/loader.js:725:27)
  at Module.require (internal/modules/cjs/loader.js:952:19)
  at require (internal/modules/cjs/helpers.js:88:18)
  at Object. (/Users/pangge/twilio/voicemail/plugin-queued-callbacks-and-voicemail/craco.config.js:1:16)
  at Module._compile (internal/modules/cjs/loader.js:1063:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
  at Module.load (internal/modules/cjs/loader.js:928:32)
  at Function.Module._load (internal/modules/cjs/loader.js:769:14)
  at Module.require (internal/modules/cjs/loader.js:952:19)
  (Use node --trace-warnings ... to show where the warning was created)
  (node:30265) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
  (node:30265) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  Could not find build file. Did you run npm run build first?

After deploying the plugin, the audio is stuck in a loop and doesn't get past the "estimated wait time" message. Customers are unable to make a callback or voicemail request selection.

The function getTask() is called by three different functions. Move the implementation into an helper.

Test procedure:
Tool: Monkey Phone-tester

1. Call to your Flex Phone Number
2. Go to voicemail, select for Callback option from the main menu choose Option #2 for entering number manually (as per https://github.com/twilio-labs/plugin-queued-callbacks-and-voicemail/blob/main/serverless/functions/inqueue-callback.protected.js#L100)
3. Enter alternate number
   code file : inqueue-callback.protected.js.
   Line: 100
   message += 'Press 2 to be called at different number';

Result:
In the Task attributes the call-back number is not a valid E-164 format ("+" sign in prefix is missing)
So, when the agent tries to place a call it gives "Dialed number is invalid. Please check the number and try again."

Hello and thanks for sharing the plugin!

I have a workflow with 2 steps, and I would like to trigger the feature only at the end if no one answers.
Should I look for the speciic event and redirect the call to /queue-menu?mode=main or what to dou suggest?

Thanks

Max

Hi I've been working with the plugin and functions and they are great. As part of my use case I noticed a couple of small issues.

In serverless -> functions -> inqueue-voicemail.protected.js line 93 should be:

({ taskSid } = taskInfo); rather than ({ taskSid } = taskInfo.taskSid);

Also serverless -> functions -> queue-menu.protected.js line 130 it might be worth initiating the task info variable as an object with a status key as if both getEwt and getQueuePosition are set to false the function fails on the next conditional when it looks for taskInfo.status. For my use case I did the following:

let taskInfo = { status: "Not Requested" };

Thanks for putting together a great solution

Hi,

I'm getting the message "Warning: Each child in an array or iterator should have a unique "key" prop", while creating a custom task type. The warning shows up when clicking the TaskListItem for the custom tasktype.

For now looks like the issue is only occurring when testing the plugin locally.

Steps to reproduce issue:

Deploy plugin locally.
Make a call to create a callback task.
Click on the task to see the details and this is where we get the warning message.

Test:

No agents are available.
User leaves a voicemail.
When an agent comes online, they pick up the voicemail task.
When they click retry, the task appears in agent's queue, but it is ringing. It is no longer a voicemail talk but a voice task.

Expected behavior:

• On Retry the new task should be created in the same channel as the original.
• If this is the intended behavior, provide documentation on flex plugins page.

This is the exact step noted from this readme section.There it is instructed to update accountSid variable. But there is no accountSid variable in appConfig.js (code 1). Assuming, I should add the extra variable I did as showed in code 1 (comment ) below.But, the react app didn't work,it didn't show any callback option or voicemail after creating the task in flex.
Step 3: Open appConfig.js with your text editor and update the accountSid variable with your account SID:
var accountSid = 'ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'

//code 1 //assuming here I have to add this line "var accountSid = 'ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'" var appConfig = { pluginService: { enabled: true, url: '/plugins', }, ytica: false, logLevel: 'info', showSupervisorDesktopView: true, };

This requires changes in:

• Serverless: in the getTime() implementation
• Plugin:

  • plugin-queued-callbacks-and-voicemail/src/components/InQueueMessaging/InQueueCallbackComponent.js

    Line 164 in fe51fa1

    const timeReceived = moment(this.props.task.attributes.callTime.time_recvd);

  • plugin-queued-callbacks-and-voicemail/src/components/InQueueMessaging/InQueueVoicemailComponent.js

    Line 242 in fe51fa1

    const timeReceived = moment(this.props.task.attributes.callTime.time_recvd);

Unable to find the voicemail recordings and callback clickable option(voicemailcomponent.js & callbackcomponent.js) in the Flex UI after accepting the task. Any changes made to this? Am I missing any here?

Test procedure:

• Make sure no agents are available in Flex
• Place a phone call
• Press 1 to access the menu
• Press 3 to leave a voice message

Result:
In the log for the serverless you should see the following:

Cannot cancel task WTxxxxxxxxxx in workspace WSxxxxxxxxxx for account ACxxxxxxxxxxxx because it is not pending or reserved.

Proposed fix:
Check the status of the task before attempting to cancel it

Suggestion for a better query map builder:

// Have this helper
const urlBuilder = (url, queries) => {
  const params = new URLSearchParams();
  Object.entries(queries).forEach(([key, value]) => params.append(key, value));
  return `${url}?${params}`;
}

// then your `action` here can be
const queries = {
  mode: 'mainProcess',
  callsid: callSid,
  cbphone: explodePhone('format', phone),
};
if (event.taskSid) {
  queries.taskSid = event.taskSid;
}
const action = urlBuilder(`${domain}/inqueue-callback`, queries);

Easier to read IMO

Originally posted by @ktalebian in #20 (comment)

Unable to find the voicemail recordings and callback clickable option(voicemailcomponent.js & callbackcomponent.js) in the Flex UI after accepting the task. Not sure if I missed something or not.