Telephones...

Wish List:

·         All phone numbers need to be able (but not required) to be tied to a person, a place, and a time.

·         Also, all should appear in one screen, even if they are tied to an address.

·         It would be great if phone types could be ranked, both by type (office/cellular/home) and by use. How do you indicate that a certain constituent prefers to be called on her cellular phone during the day and on her home phone during the evening; but in no circumstance should you call after 7 pm unless it’s an emergency?

·         I should be able to set up formatting for each country where I have a lot of customers; for those outside my local calling area, I should be able to program in the special codes that aren’t part of the local number (as in the 01144 prefix I need to connect to the U.K.).

 

Challenges:

·         In South Florida, we have the issue of many part-time residents whose phones aren’t in service for large stretches of the year—and we can’t always tell from the phone company’s automated message if the number is no longer valid or just temporarily inactive. So I don’t archive phone numbers until we have attempted to call at several different times of year, including, if possible, the same time of year as the last time we had contact with the customer.

·         Many phone numbers came into our system with no real indication of what type of phone number they are—and continue to come in that way via web orders.

·         Foreign phone numbers have no formatting.

 

Fantasy:

With my Next Gen database and connected phone system, when I call a constituent, I click a “connect” chicklet, and the appropriate number, if I haven’t selected a particular one, is attempted, followed by the next appropriate number in the record, if there is one, until I reach the customer. The database keeps success/failure records for all numbers, letting me know the last time a number connected successfully. If I want, I can look at full call logs (time, duration, userid).

 

Of course, 10 years from now, phones as distinct communication tools separate from the Internet (whatever that turns into) may be quaint memories…

 

Lucie

 

 

 

Today we’re gathering information about constituent telephone numbers and how they are used in your business.  Thinking about constituent telephone numbers in your business…

 

What are some challenges that you have surrounding constituent phones today?

Are there trends you are seeing that could impact phone functionality in the future?

What do you like about telephone functionality in existing Tessitura? 

What would you like to see changed/improved about telephone functionality?

Any other thoughts about phones, your business, and Tessitura?

 

Keep in mind that this may be more than just thinking about the storage and retrieval of telephone numbers.  Try to think overall about how your business interacts with people via phone and how you might expect Next Gen to enable this interaction.

 

Thanks!

Andrew

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

Wish List:

·         All phone numbers need to be able (but not required) to be tied to a person, a place, and a time.

·         Also, all should appear in one screen, even if they are tied to an address.

·         It would be great if phone types could be ranked, both by type (office/cellular/home) and by use. How do you indicate that a certain constituent prefers to be called on her cellular phone during the day and on her home phone during the evening; but in no circumstance should you call after 7 pm unless it’s an emergency?

·         I should be able to set up formatting for each country where I have a lot of customers; for those outside my local calling area, I should be able to program in the special codes that aren’t part of the local number (as in the 01144 prefix I need to connect to the U.K.).

 

Challenges:

·         In South Florida, we have the issue of many part-time residents whose phones aren’t in service for large stretches of the year—and we can’t always tell from the phone company’s automated message if the number is no longer valid or just temporarily inactive. So I don’t archive phone numbers until we have attempted to call at several different times of year, including, if possible, the same time of year as the last time we had contact with the customer.

·         Many phone numbers came into our system with no real indication of what type of phone number they are—and continue to come in that way via web orders.

·         Foreign phone numbers have no formatting.

 

Fantasy:

With my Next Gen database and connected phone system, when I call a constituent, I click a “connect” chicklet, and the appropriate number, if I haven’t selected a particular one, is attempted, followed by the next appropriate number in the record, if there is one, until I reach the customer. The database keeps success/failure records for all numbers, letting me know the last time a number connected successfully. If I want, I can look at full call logs (time, duration, userid).

 

Of course, 10 years from now, phones as distinct communication tools separate from the Internet (whatever that turns into) may be quaint memories…

 

Lucie

 

 

 

Today we’re gathering information about constituent telephone numbers and how they are used in your business.  Thinking about constituent telephone numbers in your business…

 

What are some challenges that you have surrounding constituent phones today?

Are there trends you are seeing that could impact phone functionality in the future?

What do you like about telephone functionality in existing Tessitura? 

What would you like to see changed/improved about telephone functionality?

Any other thoughts about phones, your business, and Tessitura?

 

Keep in mind that this may be more than just thinking about the storage and retrieval of telephone numbers.  Try to think overall about how your business interacts with people via phone and how you might expect Next Gen to enable this interaction.

 

Thanks!

Andrew

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!