Skip to content
Innovative Idea Exchange

Vega Interact Voice & SMS

Vega Interact Voice & SMS

Categories

52 results found

  1. We are a Sierra library working toward the implementation of Vega Interact SMS.

    In our preparation, we've seen testers receive multiple courtesy notice texts in quick succession, for items either due or automatically renewed on the same day.
    We understand that there are currently a couple of contributing factors for this behavior, including location-based triggering, where unlike overdue notices, all other notice types-including courtesy notices-can trigger multiple messages if the items involved belong to different shelving locations or branches.
    We’ve been told that it’s also influenced by Sierra’s wildcard behavior, which can cause the system to treat each location as…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. We're currently doing some pre-launch testing of Vega Interact SMS. A couple of our testers have seen a randomly received "default" notice that isn't tied to any notice type/email, which we hadn't configured.

    Reviewing the reporting to pull these for Support, I realized that it would be very helpful if you could search on NOTICE_TYPE (hold, courtesy, overdue 2, this weird one we're seeing, etc.) to limit to only those that you want to see, whether you're looking at the history of a single patron or several.

    It would also be useful, when that limit is not set prior to…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. We are currently testing Vega Interact SMS prior to our planned go-live in a couple of weeks. A staff tester received an unexpected text this morning, for a message type we didn't set up during the implementation (courtesy texts, because we have autorenewals enabled & we understand that's not currently available, at least to Sierra libraries).

    In trying to troubleshoot/determine the notice type, which is displayed as the Polaris code of 5_1, we're assuming it was that type of notice, because what the staff member received has the look of an unconfigured message.

    The reporting displays the item location, but…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. We would very much like to see some indication in our ILS (Sierra) that a patron has opted in to receive SMS messages.

    Even if SMS Alerts cannot be their own, unique notice type & not just supplement the patron's chosen notice preference of email or phone, the simple activation of a new field would be useful for frontline staff trying to troubleshoot during interactions with the patron.

    Even a date/time stamped Note field entry that is applied when Vega Interact SMS first authenticates against the patron's record during the opt-in process would be incredibly helpful, even more so if…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. We've recently implemented Vega Interact SMS & have been looking at the options available in the reporting portal. We'd like to see the ability to export reporting data in a variety of formats (PDF, CSV, etc.).

    This will be useful whether we need to generate a report on total activity to add to our metrics or search on activity for a single user & share that with staff at that user's branch.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The currently available reporting ranges for Vega Interact SMS offer reporting on the last 3 hours of activity, today's activity, & the last 30 days of activity.

    We'd like some additional/different options to limit ranges when creating reports. The last 3 hours of activity seems a little redundant when there's an option to view today's data.

    Ideally, we'd be able to choose the following ranges:

    Today
    Last 7 Days
    Last 30 Days
    Custom Range (for example, last 3 months)
    All Time

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. In the current release (version 1.0) of the Vega Interact Reporting tool, the name of the recipient of the notice displays for voice calls (in the Custom column), but not for text notices sent, for whom only the customer's library card number shows.

    We would like it to display for both, as many users might elect to receive text alerts at the same number (e.g. a parent & their children).

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. We've just launched Vega Interact SMS. As a Sierra library, it has frustrating that beginning with the implementation document, so much of the experience is heavily focused on Polaris tables, settings, & configuration elements.

    That seems to have continued to be the case with the reporting as currently available. For example, the notification types displayed in the reporting are based on the Polaris notification types table.

    21 = hold notice, 1st level
    1
    3 = overdue notice, 3rd level

    If instead of a numeric code, they displayed Hold notice, Overdue Notice, 3rd Level, Hold Cancellation Notice, etc. that would…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Branding is increasingly important for public libraries. So too is the reliable receipt of our communications & the distinction, in the patron's mind, between library communications & spam they might receive.

    Vega Interact SMS currently sends its text messages from the short code number 60896. We would like an option for a custom number of our own choosing to facilitate the promotion of this service & more easily identify these messages as coming from our library.

    For example the short code of 246295 can be used to spell out CINCYL. The short code of 26657 can be used to spell…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Currently, when a patron registers to receive text alerts through Vega Interact, assuming their information successfully authenticates against their patron record, they see what's shown in the attached image once they submit the opt-in form.

    Rather than a 'Success!' message or alert that they'll receive a 'welcome text' from the vendor's short code number, they see the same header text they do on the initial registration page to 'Sign up to receive CHPL account notifications by text message,' which they just did.

    We would like to see more clear indication in the wording that the registrant's information has been accepted.…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. My understanding is that currently, Vega Interact (which we only use for phone calls) is only capable of writing back calls that go through successfully as notification status = 11 (Call failed - Undetermined error).

    Our expectation previously was that the system would retry a call 3x before rolling to print. We don't currently mail print notices, so rolling to print immediately essentially means the patron doesn't get notified.

    We would like Vega Interact to add the ability to write back other notification statuses, especially in these situations:

    3 --Call not completed - Hang up
    4 --Call not completed -…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Update the verbiage used for the inbound telephone service to the correct tense for item due dates. Currently, patrons hear "Your item was due December 1st" or "Your item was due December 15th." Can we change the tense for items that are not past due to be "is"?

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. We currently have 115K+ patrons with Phone as their notice preference. Since launching the dial-in component of IPA/Vega interact Voice, we've had roughly 21K calls.

    We would like more reporting on what it is they're calling in for. Are they selecting the option to listen to their current checkouts, their holds? Are they choosing to hear library announcements? Are they navigating through multiple menu options on the same call?

    For something like the library announcements option especially, it would help us better gauge the usefulness of updating this content more frequently so it remains fresh & informative.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. We have a number of library cards that begin with letters instead of numbers. If Polaris is able to use these as valid cards, IPA should allow people with these cards to interact with the system. As it is, there is nothing they can do to interact with the system by phone.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. We have found that Polaris sends Almost Overdue & Autorenew notices by email if the patron has a valid email address on their account, even if they have selected TXT as their notification option. The only way to send an Almost Overdue notice by text is to check the "Additional TXT notice" box, which makes no sense if the patron has already chosen TXT for notices.

    Most patrons who chose TXT for notifications do so because they do not read their emails. The Almost Overdue notices are missed and late fines are incurred. Vega Interact should send Almost Overdue &…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. We have found that Polaris sends Almost Overdue notices by email if the patron has a valid email address on their account, even if the patron has chosen TXT as their notification option. The only way to send an Almost Overdue text message is by checking the "Additional TXT notice" box. Most patrons who select TXT as their notification option do so because they do not read their emails, so the Almost Overdue alerts are ignored and late fines are incurred.

    If a patron selects TXT as their notification option, the Almost Overdue & Autorenew notices should be sent by…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. I am so tired of trying to be a consortia in a stand alone environment!

    Patrons identify with their local independant library. A single opt in landing page doesn't allow for local branding to unify the experience within the website or collection site. Currently selecting the single opt in page passes you out of the domain to a generic shared page for the entire consortia. This means no library logo/color and single brand messaging.

    Not only are we sending them off brand and off site, but the Vendor (who is of zero importance to our patrons) takes up most of…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Currently, if a patron is blocked from borrowing due to too many fines and/or long overdue items they can still place hold requests. This causes issues when the patron comes into the library to check out the items and is met with a block.

    A notice type should be added where a patron gets notified when their account is blocked and they can no longer check out materials. This will help patrons understand they can still place holds, but cannot checkout until they bring their account to good standing.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. In the old Notices setup, we had two separate options for Almost Overdue SMS and Autorenew SMS, which we could (and did!) customize separately. In Vega Interact we were given one option for a combined SMS notice for both. This requires us to be more vague, and it frankly sounds odd to say 'either your items are due soon and/or they were renewed'. Please bring back both separate options!

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Patrons would appreciate the ability to freeze/thaw their currently active holds via Innovative Phone Alerts/Vega Interact.

    As a library with 120,000 patrons who receive their notices by phone & presumably also engage with the dial-in component, we would like these users to be afforded functionality similar to what patrons who manage their holds online experience.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3
  • Don't see your idea?